Skip to content

fix(TIN-5770): bound the Bazel server and label local Bazel runs - #65

Closed
Jess Sullivan (Jesssullivan) wants to merge 1 commit into
xoxd-ai:mainfrom
Jesssullivan:fix/tin-5770-bazel-server-bounds
Closed

Jess Sullivan (Jesssullivan) wants to merge 1 commit into
xoxd-ai:mainfrom
Jesssullivan:fix/tin-5770-bazel-server-bounds

Conversation

@Jesssullivan

@Jesssullivan Jess Sullivan (Jesssullivan) commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

Linear: TIN-5770

Bounds the Bazel client server and labels local Bazel runs. Rulings R470, R471 and R472 (operator answers 2026-10-26).

Rule File Change
R470 .bazelrc:1-3 startup --max_idle_secs=120. A server left by a local build or test exits after 120 s idle, not 3 h.
R471 .bazelrc build --remote_local_fallback=false. No flywheel lane is enrolled, and no endpoint is added.
R471 BUILD.bazel:8-9, docs/release-flow.md:38-41, scripts/check-package-consumer.mjs:24 The docstring names the ci-templates CI build. The release gates and the consumer hint label local bazel runs local, non-qualifying.
R472 docs/release-flow.md:74-75 The query example is bazel --batch query //..., which leaves no server.
R472 flake.nix:33 Unchanged. The banner reads .bazelversion and starts no server.

Validation (sting)

  • A logging bazel/bazelisk stub on PATH ran the flake shellHooks of vite-plugin-skeleton-colors and tinyvectors. The stub saw one call, bazel --version. nix eval of devShells.x86_64-linux.default.shellHook shows no other Bazel verb.
  • No Bazel server ran for this workspace before or after (ps). sting load1 was about 70 (budget 48), so no real Bazel command ran here. See Follow-ups for CI.
  • The repo has no Justfile, so just --list does not apply.
  • node scripts/check-release-metadata.mjs and node --check scripts/check-package-consumer.mjs pass.

Not changed

  • No try-import %workspace%/.bazelrc.flywheel: no lane is enrolled, and the plan forbids invented endpoints (wave-1 xoruby-2026 precedent).
  • CI stays on xoxd-ai/ci-templates js-bazel-package.yml (plan row 45 owns that move).

Follow-ups

  • PR CI fails at package / resolve-runner ("runner_mode=repo_owned requires explicit runner_labels_json"): fork PRs see vars.PRIMARY_LINUX_RUNNER_LABELS_JSON empty, so no Bazel step runs. Until that is fixed, CI has not exercised the new .bazelrc lines. The merge evidence is that both flags exist in the pinned Bazel version.

Not merged. Batch: plan row 43 part D (vite-plugin-skeleton-colors, xoxd-spectrogram, tinyvectors, xoxd-theme, marketing-kit).

R470: .bazelrc sets startup --max_idle_secs=120, so a server left by a
local build or test exits after 120 s idle instead of 3 h.

R471: no flywheel lane is enrolled. .bazelrc sets
--remote_local_fallback=false. The BUILD.bazel docstring names the
ci-templates CI build. docs/release-flow.md and the package-consumer
hint label the local `bazel build`/`test` lines local, non-qualifying.

R472: the release-flow query example uses `bazel --batch query`. The
shellHook banner already reads .bazelversion and starts no server.

Linear: TIN-5770
Huskycat-Receipt: v1;spec=e36b2ab282bbe840e25bc8fead5b035a6014442eef912f604b0aa8b65db1ceed;tiers=t0,t1;blobs=e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855;pending=none;host=sting
@Jesssullivan

Copy link
Copy Markdown
Contributor Author

Replaced by #66 at the same reviewed head dea0e5d. Fork PR CI cannot read repo variables, so package / resolve-runner fails here (TIN-5770).

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