Repository navigation
Unit lane cap 60 -> 80 min from the first uncensored wall (follow-up to #13445) - #13449
Closed
gunbai-bot[bot] wants to merge 3 commits into
Closed
gunbai-bot[bot] wants to merge 3 commits into
gunbai-bot[bot] wants to merge 3 commits into
Conversation
The restored rust-unit-tests lane (gunbc#12951) hit its 40-minute step cap on main's population with every test that ran passing (job 111941683683), so no required run has passed since. The cap's own rule (largest observed fleet wall x 1.5, to the next 5) applied to that censored 40 gives 60; witnesses.yml is the generated projection of the same two values. The cost shape (cost_debt_* and reach_base_standings tests each resolving a live .dag graph) is the real defect and is named in the comment for its own repair. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Records the unit-lane occurrence in gunbc.recurring_failure_mode shared_precondition_re_derived_once_per_claim_frame (per-#[test] resolve of a live .dag graph in the cost_debt_* and reach_base_standings tests) and cites that row by symbol from compiler_gate_unit_test_timeout's comment. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…90 (job) gunbc#13445's own required run finished the full unit population in 52m51s under the 60-minute cap, above the two-thirds re-derive line; by the cap's rule that gives 80. witnesses.yml is the generated projection of the two values. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Superseded by #13448 (the same authority, compiler_gate_unit_test_timeout, set to 75/85 from its own uncensored measurement), which is the single cap-derivation PR. Closing to keep one route. — sent from neat-boar-16 |
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
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.
Follow-up to #13445, stacked on it (the diff includes #13445's commits until it lands).
#13445 raised the
rust-unit-testsstep cap from 40 to 60 using a CENSORED 40-minute wall, and said 60 was provisional. Its own required run then executed the full population and the step finished in 52m51s: the first uncensored reading (therust_unit_testsstep of #13445's run). That is above two thirds of 60, the cap's re-derive line. By the rule ingunbc.compiler_gate_workflowcompiler_gate_unit_test_timeout(largest fleet step wall x 1.5, rounded up to 5), the step cap is 52m51s x 1.5 = 79.3, so 80, and the job cap is 80 + 10 = 90.witnesses.ymlis the generated projection of those two values.The cost shape remains the real defect, rostered in
gunbc.recurring_failure_modeshared_precondition_re_derived_once_per_claim_frameby #13445.🤖 Generated with Claude Code