You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
FLOW-003 QM-09: compile-once — one --workspace test build, nextest archive, K shards fanned across all runners (FLOW-003 v2.1 §row QM-09) #4527
Operator 2026-09-27, trunk-based target design. Order of work: measure (#4513), then build once (QM-09), then generated shared files (#4526), then tiers (QM-10/11), then retire folds once main has been green 7 days in a row. Spec: docs/specifications/FLOW-003-queue-and-release-cycle-model.md (branch flow-003-v2.1). Targets: CI p50 ≤10 min for code and ≤2 min for docs; lead time under 1 h; one build per PR. This row changes .github/workflows. The operator's order of work authorizes the change; its PR still carries a quorum and a before/after timing receipt.
Reopened. This issue carries no agent marker, so it may have been filed by a human, and agents never close a human-filed issue. A 3-lane review quorum (3/3, planted control passed) ruled to reopen it and to move or re-home it within the epic budgets instead of parking it.
Re-homed under ISSUE-TREE-001 (epic #4540 had no live owner). Owner: la-0.72, the live look-ahead session for 0.72.0, which matches this issue's milestone. Replaces owner:aprender-a7.
QM-09 compile-once: paired full-tier proof and decision (Refs #4505)
BEFORE run 37966946909 @af58dfccff (main) vs AFTER run 37966950775 @ddd8311bcc (branch la-72/4527-compile-once). Both were workflow_dispatch, tier full on all 3 shards.
Verdict set: identical.
Lib junit: 83994 / 83994, all pass, no duplicates.
Also identical: nextest partition summaries, the explicit list (102 ids, 664 run), cargo-test lines (6120) and x86-main guard rows (122).
4 guard rows fail the same way in both dispatch runs: ratchet guards that cannot resolve a base on workflow_dispatch. Main's push run at af58dfc is green.
Wall time: slower.
Run wall: 38 → 72 min.
Shard + build runner-seconds: 5572 → 6994 (+25%).
Each shard spends 1021–1068 s fetching the 891 MiB nextest archive and saves about 620 s of compile.
The fetch is a single-stream GET of the artifact blob, measured at about 1.1 MiB/s per stream. 4 parallel ranges ran 3.85x faster.
Decision (quorum, 3/3): stop.
A parallel ranged fetch would only bring wall time to about even, because the build job runs ahead of the shards. It would cut runner-seconds by about 10%, which is not worth another sign-off round plus a paired run.
merged into #5318 (master ticket for epic #4540; triage rule 7b, 2026-10-14). It is a checklist row there; reopen this issue when work on it starts or its PR opens.
Activity
perf(guard): drop a dead find over all of /tmp from check_crux_ollama…
perf(guard): two quadratic cargo-free guards made linear, with identi…
perf(guard): check_include_files 33 s → 2.7 s — read git ls-files onc…
perf(guard): check_unwired_capabilities 52 s → 18 s — one awk over al…
perf(guard): shell_lint_ratchet 29 s → 8.8 s — bashrs per file, 4 at …
perf(guard): crux_inference_judge 434 s → 188 s — F6 mutants run 6 at…
perf(guard): check_silicon_coverage — gh jobs fetch 8 at a time, 58 s…
perf(guard): check_crux_serve_code 107 s -> 30 s — teardown TERM/KILL…
perf(guard): check_perf_claims_cite_receipts 88 s -> 6 s — one batche…
perf(guard): private_root classifiers match with [[ =~ ]] instead of …
perf(guard): tree_reader_tests prefilters src with grep -l instead of…
perf(guard): claim-citation window skips the resolver when it has no …
perf(guard): apr_bin_pinned strips quoted spans in bash, not a sed fo…
perf(guard): resolve_includes MOD_DECL no longer restarts inside whit…
22 remaining items
noahgift commentedon Oct 9, 2026
Reopened. This issue carries no agent marker, so it may have been filed by a human, and agents never close a human-filed issue. A 3-lane review quorum (3/3, planted control passed) ruled to reopen it and to move or re-home it within the epic budgets instead of parking it.
Agent: aprender-a3
noahgift commentedon Oct 9, 2026
Re-homed under ISSUE-TREE-001 (epic #4540 had no live owner). Owner: la-0.72, the live look-ahead session for 0.72.0, which matches this issue's milestone. Replaces owner:aprender-a7.
Agent: aprender-df
ci(QM-09): shard 1 stages only the explicit list; per-job push-arm rows
noahgift commentedon Oct 9, 2026
QM-09 compile-once: paired full-tier proof and decision (Refs #4505)
BEFORE run 37966946909 @af58dfccff (main) vs AFTER run 37966950775 @ddd8311bcc (branch
la-72/4527-compile-once). Both were workflow_dispatch, tier full on all 3 shards.noahgift commentedon Oct 14, 2026
merged into #5318 (master ticket for epic #4540; triage rule 7b, 2026-10-14). It is a checklist row there; reopen this issue when work on it starts or its PR opens.