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
Commit 6b0c69e
Browse filesBrowse the repository at this point in the historyBrowse files
improvement(ci): track flaky checks daily and fix the live flakes (#9038)
## Summary
- Add a daily `ci-flakes` workflow (`scripts/report-ci-flakes.ts`): a job that failed on a CI attempt and passed on a re-run of the same commit files one `ci-flake` issue per failing test (Vitest `FAIL` lines and the E2E harnesses' `[Suite] FAIL` lines), or per job when its log names none. Occurrences are keyed by job id, so the overlapping 3-day lookback never double-counts, and a closed issue reopens when its flake recurs. Dependency-free, so the job needs no install
- Fix the live flakes found in the last two weeks of re-runs:
- GitHub rate-limit reset test: pin the clock; a second boundary between building the header and reading it gave 899000
- OAuth token and token-family integration tests: import the auth graph statically, so its cold load (up to ~43s on a slow runner) no longer counts against the first test's 30s timeout
- stop-after E2E: wait for the sibling-pause claim until the resume request settles, not a fixed 2s that a slow `next dev` round trip outlasts
- HTTP E2E readiness: 300s → 600s; healthy cold compiles take 60–185s and a degraded runner ran past 300s with every step 3–6x slower
- Reconciliation-window integration test: print each scan's plan when a window statement reads past the bound, so its next failure names the cause (diagnostics only; the cause isn't confirmed yet)
- Mobile e2e and usage-log flakes were already fixed by later commits, so nothing changes there
- Testing rules: a short section on the flake workflow and how to fix one (no retries, longer timeouts, or skips)
0 commit comments