[CI] Fix offline paired-fixture deadline failure - #63
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
@codex review |
|
Independent Luna/max review APPROVE on exact 513ed85, no findings. Reviewer reproduced the head-test/base-script red (exit1), verified exhaustive disjoint 146-test classification (19/106/15/6), ran all four actual race partitions (71.379s/31.295s/53.794s/38.927s), full offline experiment script (4m41.22s), generated positive/failure propagation tooling tests (29.551s), vet/syntax/diff checks, and canonical guide consistency. Checkout stayed clean/head unchanged. Hosted CI run34196653294 job101965765302 succeeded. Fresh Codex review requested; merge remains held until a timestamped exact-current-head completion and all findings are checked. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 513ed85860
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
P2 resolution for Codex finding on b15741218d18bb7dca449228ecc6f9b26ad7563d. Red before the script correction: Green after the correction: the same test exited 0 in 31.457s; its race form exited 0 in 32.254s. Generated positive Test, Example (with an Output directive), and Fuzz seed sentinels each ran exactly once; generated negative Test, Example output mismatch, and Fuzz seed failure each propagated through one invocation with no retry. Final verification on the pushed head:
No live resources or credentials were used. Fresh independent review, hosted CI, and exact-head Codex re-review remain coordinator-owned gates. |
|
@codex review |
|
Codex Review: Didn't find any major issues. Swish! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Closes #61
Ref #1
Summary
The G01
g01_pair_fixturelivecanary collection/listener workload exceeded its existing per-process 120-second deadline because the non-terminal suite had accumulated more work; this PR splits only that workload into two explicit static, exhaustive, disjoint groups. The existing terminal behavior and terminal-storage groups,g01_pair_fixture/live-helper exclusions, Go 1.26.8 pin, race detector,-count=1, 120-second process bounds, sequential failure propagation, and one tagged vet invocation are preserved.Diagnosis
The reported public CI failure is run 34193163898, job 101955210094, whose metadata shows the reviewed offline experiment step failed after the preceding checks passed. The frozen local Go 1.26.8 race measurements on the pre-fix command were:
TestObserveCancellationAndApprovalExpirycompleted locally in 0.08s, so the observed CI line showing it running for 0s was not treated as proof of an individual hang.TDD evidence
Red before implementation
Exit status was 1 because the generated paired-collection witness still ran through the old unsplit
-skip '^TestPairedTerminal'invocation, while the new partition invocation was absent.Green after implementation
The generated positive witnesses mark and execute each of the four groups exactly once; generated failures stop the corresponding group and propagate a non-zero result.
Group timing and coverage
Focused pinned Go 1.26.8 race runs after the split completed as follows:
The final sequential offline check also passed:
Each G01 process stayed below 120s; the G02 default and reviewed command checks also passed (24.732s, 1.480s, and 2.255s, with the existing synthetic command reporting no test files).
Tagged
go test -list '^Test'classification is exhaustive and disjoint over 146 top-level tests:^TestPairedexcluding^TestPairedTerminal).^Testexcluding^TestPaired).Verification
GOTOOLCHAIN=go1.26.8 go test -count=1 ./...— exit 0; root packages passed, scripts package 37.870s.GOTOOLCHAIN=go1.26.8 go test -race -count=1 ./...— exit 0; root packages passed, scripts package 42.557s.GOTOOLCHAIN=go1.26.8 go vet ./... && make fmt-check— exit 0.bash -n scripts/check-offline-experiments.sh && git diff --check— exit 0.Safety and rollback
No tests were dropped, retried dynamically, or given a wider deadline. No live runners, Docker/Lima/context, GitHub App, Keychain, launchd, credentials, or private logs were touched; all fixtures remain local synthetic tests and the existing live-helper exclusions remain in force.
Rollback is source-only: revert commit
513ed858607094226c1482f4615d8c912c6a1720or close this PR without applying it. The change creates no runtime state, journal migration, runner resource, or online rollback obligation.Remaining gates
The exact pushed head is
513ed858607094226c1482f4615d8c912c6a1720. Independent review, required hosted CI, and an exact-head GitHub Codex review remain required before merge; this PR does not claim live acceptance, parent #1/#2 completion, or Project Done.