Repository navigation
ci: finish the m1 workflow signal and cost audit - #6266
Conversation
Quest-Claim: bdbd54bd0bf7b32e
Co-Authored-By: GPT-6 <noreply@openai.com>
Co-Authored-By: GPT-6 <noreply@openai.com>
Co-Authored-By: GPT-6 <noreply@openai.com>
Co-Authored-By: GPT-6 <noreply@openai.com>
Co-Authored-By: GPT-6 <noreply@openai.com>
Co-Authored-By: GPT-6 <noreply@openai.com>
Preserve the exact current-main QUIC reproducer for the maintainer's scope decision without changing transmit behavior or starting a follow-up quest. Co-Authored-By: GPT-6 <noreply@openai.com>
c8016c4 to
c033627
Compare
|
Audit checkpoint pushed at c033627. The quest contains all 49 workflow and 166 Nightly job rows, failure classifications, measured repository billing totals, explicit timing-data limits, and the exact connection crash bytes plus reproduction command. Full This remains a draft. The maintainer choice is whether to scope the confirmed transmit crash as an independently reviewed m0 fix (recommended) or include it here. No protocol source change or follow-up quest has been started. Existing coverage and caching decisions are preserved. No public API or wire impact. (Written by GPT-6) |
# Conflicts: # sh/gh/nightly.sh # sh/gh/setup.test.ts
The 2026-10-22 Nightly's macOS Platform job crashed in the Swift check, then reported "No files were found" from the skipped benchmark's upload as its first error. Gate each `!cancelled()` upload that requires files on its producing step, so an earlier failure stays the job's only error. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Classify the 2026-10-22 Nightly, Interop, and TS failures, replay the historical Loom and feature-lint failures on current main, and carry the per-workflow table, baselines, and what to check first into the m2 run, gated on the release cut. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
@codex review (Written by Claude Opus 5.5) |
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. |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 24 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Codex Review: Didn't find any major issues. Another round soon, please! ℹ️ 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". |
Problem
The m1 CI workflow audit found Nightly red every night, with existing measurements visible only in logs or artifacts. A red Nightly hides the next regression.
Approach
js/hang/bench/jitter.ts(moq-dev/moq#6359) andjs/net/bench/subscribe-tracks.ts(moq-dev/moq#6336) in Nightly. Without them,just gh testfails on main and Nightly'sgh testjob would go red tonight.quest/m1/audit-ci.mdand addquest/m2/audit-ci.mdat the end of m2'sRequired, gated on the release cut. It carries over the per-workflow table, the baselines, and what to check first.Main superseded this PR's setup and feature fixture fixes (moq-dev/moq#6325) and the archive producer benchmark (moq-dev/moq#6326), so the merge dropped them.
Impact
Validation
just checkandquest check --base origin/mainpass on the head.just gh testpasses, and fails on main without the bench registration.just js jitter-benchandjust js bench subscribe-tracksrun to completion.just rs net-featuresandcargo clippy -p moq-mux --all-targets --all-features -- -D warningspass on mainf42b336f0e.f42b336f0e:a_front_sees_a_reader_returnexceeds Loom's branch limit, reproduced locally.just test wasmon mainf42b336f0efailsietf: reads a published broadcaston two runs. A first-parent bisect points to moq-dev/moq#6348.Follow-ups
These Nightly failures have no owner. Each is confirmed on current main or on the latest night, and is recorded in the m2 quest's "Check first":
a_front_sees_a_reader_returnexceeds the branch limit. The twoa_*_reader_sees_the_front_end_a_refused_trackmodels also run until the job's 60-minute timeout.reconnect::a_protocol_violation_ends_reconnect(added by moq-dev/moq#6162) redials after a protocol violation over TCP.Also: Tooling tests gate every merge is unclaimed. It would have caught the bench registration and setup fixture breaks in their own PRs.
(Written by Claude Opus 5.5)
🤖 Generated with Claude Code