Repository navigation
CI perf: full tier (41 legs) runs on every push to main, not just nightly #1414
Description
The ci.yml header says the full tier is nightly, but e2e-full, yarn-berry-full and cargo-vex-matrix-full also run on every push to main: 41 legs per landing, most done in under a minute, which came to 1,845 of the 2,330 push-run jobs across 45 pushes on Oct 10-11. Gating them like e2e-docker (schedule, workflow_dispatch and the v5 integration PR) keeps the full tier on the nightly and release-qa dispatches; the trade-off is that a regression only that tier catches shows up at the next nightly instead of on the landing. PRs here are collaborators-only, so could a maintainer cherry-pick this signed commit (it also updates the two scheduling tests that pinned the old condition, and scripts/tests pass) or grant PR access? main...austenstone:socket-patch:ci-full-tier-nightly
Activity
mikolalysenko commentedon Oct 12, 2026
[agent] Triage: confirmed on origin/main 1779317.
.github/workflows/ci.yml:2032(e2e-full),:2286(yarn-berry-full) and:2426(cargo-vex-matrix-full) only exclude pull_request and merge_group, so they run on every push to main. Push run 38197830089: 41 of its 50 non-skipped jobs are these legs (~21 runner-minutes wall, ~41 billed job-minutes). The nightly schedule and workflow_dispatch already cover this tier.[agent] Claiming this issue (shared root cause: full-tier jobs gated on 'not PR/queue' instead of nightly/dispatch). Branch: agent/fix-ci-full-tier-nightly. Claim-ID: 2026-10-12T03:50:35Z-8f4246
Generated by Claude Code
mikolalysenko commentedon Oct 12, 2026
[agent] Fix in #1415.
Generated by Claude Code
CI: skip e2e binary upload on lean pushes
mikolalysenko commentedon Oct 12, 2026
CI profiler — fresh numbers (window 2026-10-11 15:38 → 2026-10-12 04:00 UTC, 17 push-to-main CI runs, all jobs fetched with
filter=all)e2e-full*/yarn-berry-full/cargo-vex-matrix-fullci-ok: p50 3.43 / p90 3.82 min. Ane2e-fullleg is the last job beforeci-okin 10 of 17 runs, so gating it should also take a little off the push verdict (unmeasured;coveragewould become last).release-qadispatches keep the tier, so coverage stays at nightly.Example runs: 38197830089, 38187527055, 38186163932. The profiler will report the before/after on the dashboard (#1182) once #1415 merges.
Generated by Claude Code