Skip to content

svelte: fix consumer test module setup after first CI run (part of #6178) - #7004

Merged
TrapsterDK merged 2 commits into
mainfrom
svelte-consumer-6178
Nov 5, 2026
Merged

TrapsterDK merged 2 commits into
mainfrom
svelte-consumer-6178

Conversation

@TrapsterDK

Copy link
Copy Markdown
Collaborator

Part of #6178.

Fixes found by running the consumer test on CI (linux_x86_64) for the first time:

  • Root module of the nested consumer now carries the rules_py archive_override (non-root overrides are ignored), pinned from versions.bzl and MODULE.bazel.
  • The copied preset bazelrc now points @rules_dx// flags at the renamed @acme_rules// repo.

CI evidence (evidence.yml, linux_x86_64, //svelte/tests/consumer:app_consumer_test):

  • 41986321828: failed, rules_py not in BCR (fixed here)
  • 41987413230: failed, @rules_dx//config:clippy_output_diagnostics not visible (fixed here)
  • 41988645073: still failing, 3 CI rounds used. fmt and clippy tests pass. Not run locally (nested Bazel).

Remaining, seen in 41988645073:

  1. svelte_build site_dist: Rolldown The "fileName" or "name" properties of emitted chunks and assets must be strings that are neither absolute nor relative paths, received "../../../../../../../../execroot/_main/bazel-out/k8-fastbuild/bin/index.html". The app sits in the consumer root package; the entry resolves through the sandbox symlink outside the root in svelte/rules/svelte_tool.mjs.
  2. dx check/lint/format in the consumer: "Biome needs a config"; the consumer needs a biome.json plus biome_config aspect hint.
  3. dx check generate: gazelle fails loading @rules_dx//gazelle/julia (no such attribute 'package_name' in 'julia_binary'), a rules_dx bug when consumed externally.

🤖 Generated with Claude Code

https://claude.ai/code/session_011u9TXHDZrfmzFQ2WT8QAKK

@TrapsterDK
TrapsterDK merged commit 693f485 into main Nov 5, 2026
1 of 2 checks passed
@TrapsterDK
TrapsterDK deleted the svelte-consumer-6178 branch November 5, 2026 07:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant