Skip to content

xtask/tests/cli.rs: the all-gates selftest case asserts the dispatcher reached a verdict - #726

Merged
MattJackson merged 2 commits into
predevfrom
lane-selftest-dispatcher
Oct 10, 2026
Merged

MattJackson merged 2 commits into
predevfrom
lane-selftest-dispatcher

Conversation

@MattJackson

Copy link
Copy Markdown
Collaborator

The shared red: gate:test:workspace ... (nextest: xtask::cli::selftest_runs_every_registered_gates_red_proof)

xtask/tests/cli.rs::selftest_runs_every_registered_gates_red_proof required xtask selftest over EVERY registered gate to exit 0. Each gate's red proof is planted over the tree the test runs in. When a gate is already red on that tree, its selftest reports "THE PROOF IS IMPOSSIBLE — the rows this case covers were ALREADY RED on the unplanted tree". So this one nextest case goes red on every branch that reds any gate at all, under one shared name. The test:xtask-selftest check already reports that same failure, and it names the gate:

PR gate whose selftest is impossible on the branch
#502 plane-abi-neutrality
#648 unconstructed
#634, #673, #703 linked-dropped-features (unified-deps red on the branch)
#621 settings-leak (scan-floor)
#627 no-deferral (discovery floor)
#629 tracing (scan-floor 971 < 980)

The case's subject is the DISPATCHER (the file header says so). It now holds the all-gates arm to 0 or 1, the same way gate --all is held two cases above it, because 2 (bad arguments) and 3 (could not run) are the answers that mean the arm never judged. It keeps selftest segregation and gate segregation --selftest at 0. Each gate's proof is still judged gate by gate in test:xtask-selftest.

This removes one duplicate deny line, and about 480 s of nextest, from every branch with a red gate. It does not make any of those branches green, because each one still owes its own gate.

…r reached a verdict, as gate --all does

selftest_runs_every_registered_gates_red_proof required `xtask selftest` over EVERY gate to exit
0. Each gate's red proof is planted over the tree the test runs in, and a gate already red on that
tree reports its proof IMPOSSIBLE, so this one nextest case went red on every branch that reds
any gate, under one shared name (plane-abi-neutrality on #502, unconstructed on #648,
linked-dropped-features on #634/#673/#703, settings-leak on #621, no-deferral on #627, tracing on
#629), beside the test:xtask-selftest check that already names the gate. The case's subject is
the dispatcher: it now holds the all-gates arm to 0 or 1 (2 and 3 stay refused), and keeps the
named segregation selftest at 0.
@MattJackson
MattJackson enabled auto-merge October 10, 2026 05:52
@github-actions

Copy link
Copy Markdown

promote into predev: BOARD @6aad3f5ae: 0 failing test row(s), 11 DENY row(s)

DENY rows (11)

gate row detail
construction one-pick-site 3 production call site(s) of 'pick_among(' (ceiling 2): crates/busbar-kernel-egress/src/walk.rs:298; crates/busbar-llm/src/engine/exhaustion/fallback.rs:120; crates/busbar-llm/src/engine/pipeline.rs:8
kind-isolation kind-isolation:deps 3 finding(s), 94 shipped edge instance(s) over 31 class(es), 94 declaration(s); 57 '[[dep]]' row(s), 0 question(s): unlisted-dep-edge legacy -> plane busbar-llm -> busbar-plane-llm is a shipped edge w
kind-isolation kind-isolation:test-deps 3 finding(s), 35 test edge instance(s) over 21 class(es), 35 declaration(s); 20 '[[dep]]' row(s), 0 question(s): unlisted-dep-edge cleanliness -> legacy busbar-core-admin -> busbar-a2a is a test edge
kind-isolation kind-isolation:law0 18 finding(s) over 14 neutral crate(s): law0-rise busbar × auth 51 hit(s) against a ceiling of 46: this landing grew a neutral crate's instance vocabulary. Ceilings only fall (measured on predev f830f
kind-isolation-ship kind-isolation:deps 11 finding(s) over 94 shipped edge(s): ship-edge kernel -> hooks busbar-kernel -> busbar-hook-ranking is 'not-allowed': the architecture grants no kernel -> hooks edge, and the ship criterion is the a
kind-isolation-ship kind-isolation:test-deps 10 finding(s) over 35 test edge(s): ship-edge cleanliness -> export busbar-core-admin -> busbar-export-prometheus is 'not-allowed': the architecture grants no cleanliness -> export edge, and the ship
kind-isolation-ship kind-isolation:law0 18 finding(s) over 14 neutral crate(s): law0-rise busbar × auth 51 hit(s) against a ceiling of 46: this landing grew a neutral crate's instance vocabulary. Ceilings only fall (measured on predev f830f
kind-isolation-ship kind-isolation:faces 2 finding(s) over 40 crate(s): foreign-entry crates/busbar busbar is kind 'root' and implements 'Transport' 1 time(s) in shipped source — the entry face of kind 'transport'. A trait implementation is
kind-isolation-ship kind-isolation:legacy-drain 3 finding(s): transitional-live qa/kind-isolation.toml 'busbar-a2a -> busbar-core-admin' (legacy drain: the retiring A2A engine's tests drive the admin surface that drained into the cleanliness tier)
ship-ready ship-ready:ship-twin 'kind-isolation-ship' is not green: kind-isolation:deps (a dependency the architecture does not grant is still in the graph); kind-isolation:test-deps (a dependency the architecture does not grant is
structure-lint structure-lint:plane-dup:unledgered 22 finding(s): PLANE-DUPLICATE (module): 'config.rs' — a2a:crates/busbar-a2a/src/a2a/config.rs decisions:crates/busbar-plane-decisions/src/config.rs voice:crates/busbar-voice/src/config.rs (the ledger

Judged against base 6ca8584fc: 0 new red, 0 worse, 5 standing (excused).

tests passed: 11373, failed: 0. Run: https://github.com/GetBusbar/busbar/actions/runs/38028993350 . Artifact verdict-6aad3f5ae648757cb228884c5c8870f8c93fb225 (failures.json, junit.xml, raw.log; 90 days).

@MattJackson
MattJackson added this pull request to the merge queue Oct 10, 2026
Merged via the queue into predev with commit 0517441 Oct 10, 2026
8 checks passed
@MattJackson
MattJackson deleted the lane-selftest-dispatcher branch October 10, 2026 17:13
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