Repository navigation
Delete flaky test disposition_kernel_aligns_on_discriminator_fixture (hits #6239 wall, no value) - #6324
Merged
Conversation
This sole test in mod floor_disposition_kernel_alignment (cli_run.rs) ran the floor-disposition analysis, which typechecks the gunbc module closure live — and that hits the #6239 compile-wall: per-module typecheck attribution measured gunbc.ci_deploy_access at 416s (7 min) for a single module, with the test spending >9 min and never finishing. It was the sole reason `cargo test --workspace` appeared to hang (deterministic, single-threaded reproducible), compounded by its std::env::set_current_dir cwd-mutation racing under parallel execution (#5971 class). No value and slated for deletion (operator, 2026-07-06). Floor-disposition coverage is exercised in the floor; the real fix is the compile-wall itself (owned elsewhere). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Re: "CI FAILING (1 failing)" — the failing check is
I've re-run the failed job; the sccache is now primed by this run's compilation, so clippy should finish back under 30m. No code fix applies to this PR — the deletion is exactly what was asked. If the gate keeps grazing 30m under cold-cache storms tree-wide, that's a separate rust-gate-budget concern (same class as the floor budget), independent of this change. — sent from lively-raven-355 |
briansrls
added a commit
that referenced
this pull request
Jul 6, 2026
…6324) This sole test in mod floor_disposition_kernel_alignment (cli_run.rs) ran the floor-disposition analysis, which typechecks the gunbc module closure live — and that hits the #6239 compile-wall: per-module typecheck attribution measured gunbc.ci_deploy_access at 416s (7 min) for a single module, with the test spending >9 min and never finishing. It was the sole reason `cargo test --workspace` appeared to hang (deterministic, single-threaded reproducible), compounded by its std::env::set_current_dir cwd-mutation racing under parallel execution (#5971 class). No value and slated for deletion (operator, 2026-07-06). Floor-disposition coverage is exercised in the floor; the real fix is the compile-wall itself (owned elsewhere). Co-authored-by: Brian Searls <briansrls@gunb.ai> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
briansrls
pushed a commit
that referenced
this pull request
Jul 6, 2026
briansrls
added a commit
that referenced
this pull request
Jul 6, 2026
* WIP: dedup dag.dag mvp1 fn families into parameterized cores * WIP: dedup dag.dag mvp1 fn families into parameterized cores * Dedup dag.dag mvp1 fn families into parameterized cores. Collapse five repeated stamping clusters (arrow-with-body nodes, target-model bundles, grammar token sequences, grammar-relation rows, statement prefix tokens) into shared parameterized cores with thin per-family wrappers, preserving explicit control-fixture operands at instance sites. Co-authored-by: Cursor <cursoragent@cursor.com> * Demand-driven realize: typecheck as memoized recursion over import edges (byte-identical, width=1) (#6306) * WIP: ci timeout investigation * trace_mark: stage-boundary gantt marks through the v1 compile pipeline One new registry intrinsic trace_mark(label) -> Unit (the record_source_chars_index_lookup precedent: registry row in 04_method.dag, realization in runtime_rust.dag -> v1_rt, interpreter arm for totality). Nine marks at the known segment boundaries of the compile pipeline (frontend/normalize/reconcile/analyses/emit begin+done, dag collect/serialize), so every run log carries a natural Gantt: [gantt] compile.reconcile.done t_ms=... rss_mib=... Consecutive marks define the segments; rss_mib rides along for the memory curve. Motivation: the whole-tree compile runs >60 min single-threaded with zero output after "resolved N sources" — CI runs die inside it blind (operator request 2026-07-05: checkpoints + a general logging system). Marked bridge, interim by design: dissolves into the v2 per-RealizedStep CostAccount (std.realization_measurement) when the realization-measurement carrier is inhabited. Authority edits (.dag) land with hand-synced generated seed (.rs) per the #5867 precedent — regen is currently blocked on main (#6291); re-verify at the next regen window. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * WIP: ci timeout investigation * WIP: ci timeout investigation * WIP: ci timeout investigation * WIP: ci timeout investigation * WIP: ci timeout investigation * WIP: ci timeout investigation --------- Co-authored-by: Brian Searls <briansrls@gunb.ai> Co-authored-by: Claude Fable 5 <noreply@anthropic.com> * Delete flaky test disposition_kernel_aligns_on_discriminator_fixture (#6324) This sole test in mod floor_disposition_kernel_alignment (cli_run.rs) ran the floor-disposition analysis, which typechecks the gunbc module closure live — and that hits the #6239 compile-wall: per-module typecheck attribution measured gunbc.ci_deploy_access at 416s (7 min) for a single module, with the test spending >9 min and never finishing. It was the sole reason `cargo test --workspace` appeared to hang (deterministic, single-threaded reproducible), compounded by its std::env::set_current_dir cwd-mutation racing under parallel execution (#5971 class). No value and slated for deletion (operator, 2026-07-06). Floor-disposition coverage is exercised in the floor; the real fix is the compile-wall itself (owned elsewhere). Co-authored-by: Brian Searls <briansrls@gunb.ai> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Brian Searls <briansrls@gunb.ai> Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: gunbai-bot[bot] <289086189+gunbai-bot[bot]@users.noreply.github.com> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Deletes the sole test in
mod floor_disposition_kernel_alignment(src/v1/stage0/src/cli_run.rs) — a self-contained#[cfg(test)]leaf mod, 298 lines, zero external references.Why
This one test was the culprit behind the "flaky infra"
cargo test --workspacestalls. It runs the floor-disposition analysis, which typechecks the gunbc module closure live — dragging the #6239 compile-wall into the default test run. Per-module typecheck attribution caught it:The test spent >9 min and never finished — deterministic (single-threaded reproducible), not infra flakiness. Its
std::env::set_current_diralso raced under parallel execution (#5971 class), adding the non-deterministic ENOENT layer.Operator directive (2026-07-06): no value, slated for deletion. Floor-disposition coverage is exercised in the floor; the real fix is the compile-wall itself (owned elsewhere).
🤖 Generated with Claude Code