Repository navigation
ROADMAP §1: floor wall-clock measured gap (26m → <1min, resolve-phase incrementality) - #5711
Merged
Merged
Conversation
… incrementality) Profiled the CI floor: the single `gunbc ci` step is 26m, of which ~518s re-resolves ALL 870 witnesses cold every run, plus a second discovery-corpus pass (~275s) — a full recompute regardless of what the PR changed. On a one-file PR ~99% of that resolve is redundant (§2). Adds the measured grounding to §1 and names three levers the roadmap did not have explicitly: resolve-phase affected-set pruning (the existing selection items applied to the resolve phase, not just compile/test), killing the within-run double-resolve, and profiling the 518s resolve for the known resolver pathology. Re-frames §2 P3 (resolve-cache "core ask"): that is the WARM ~18% lever, measured net-negative for cold-dominated CI; the <1min target rides incrementality (don't resolve what didn't change), not caching. ROADMAP.md regenerated from the authority (drift-gate green). Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Operator asked why CI is slow and noted the ~26m floor should be <1min. This adds the measured grounding to ROADMAP §1.
What I measured
The single
gunbc cistep is 26m (run-time, not queue). Step-level profile:run_discovery_corpuspass (within-run double-resolve)On a one-file PR, ~99% of that resolve recomputes witnesses whose inputs did not change — the §2 redundancy, un-inhabited.
The change (roadmap only)
Adds a §1
Floor wall-clockgroup with the measured numbers + the <1min target, and names three levers the roadmap did not have explicitly:budget_roster~450x its twin)Re-frames §2 P3 (resolve-cache, labeled "core ask, ~18%"): that is the warm lever and was measured net-negative for cold-dominated CI. The <1min target rides incrementality (don't resolve what didn't change), upstream of caching. Flagged for operator review — does not delete the §2 item.
ROADMAP.md regenerated from
roadmap_authority.dag(drift-gate green; verified regen == committed).🤖 Generated with Claude Code