CI cli-typecheck lane flakes red: 30-minute job budget has no headroom over its ~29-minute baseline
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, typescript
- Domain
- ci-cd
Research direction
Inspect the cli-typecheck matrix entry in .github/workflows/ci.yml and compare its timeout with the documented CI run and recent green baselines. Update the job budget so the lane has adequate headroom, then verify the workflow configuration and confirm the release-gates lane is no longer canceled at the current baseline duration.
Written by the indexing model from the issue text.
Description
Summary
CI run 32914329943 (push to main, 8fe49f0e) went red: the Full release validation (CLI tests, benchmark history, and workspace typecheck) lane (cli-typecheck) was killed by its job-level timeout_minutes: 30 budget, which failed the release-gates aggregator. Every other lane passed.
Evidence
- Job 98015815388 ran 00:20:43 -> 00:51:00 UTC (30m17s) and ended with
##[error]The operation was canceled.mid-step inValidate release lane. - No test failed: the log shows only passing tests right up to the kill. The lane was making steady progress, not hanging — the last four tests before the kill each legitimately take 48–57s (
why reports the diagnosis...56.8s,events returns bounded lifecycle events...50.0s,snapshots lists checkpoints...49.8s,timeline surfaces frame numbers...48.1s). - The lane's baseline duration in the last three green runs on main is already at the cliff edge:
- 32898410681: 29m19s (41s of headroom)
- 32888716120: 27m34s
- 32884594350: 29m19s
Root cause
The cli-typecheck lane's wall-clock budget (30 min) no longer has meaningful headroom over its honest baseline (~28–29.5 min). Ordinary shared-runner jitter is enough to push it over, so the lane fails nondeterministically with zero code defects. This is the same shared-runner-budget flake class as #851 and #864, at the job level.
Fix
Raise the cli-typecheck matrix entry's timeout_minutes in .github/workflows/ci.yml from 30 to 60, giving ~2x headroom over baseline — consistent with the generous budgets of the other lanes (package-gates 45, runtime lanes 75) and still tight enough to catch a real hang. No gate, test, or assertion is weakened.
🤖 Generated with Claude Code
- Dominant language
- TypeScript
- Stars
- 85
- Forks
- 18
- Avg merge
- 11h 10m
- Merged PRs (30d)
- 194
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from monad-developers/ultrafuzz
-
deferred-post-v0.1
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
monad-developers/ultrafuzz#724 · 3 comments ·
-
deferred-post-v0.1
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
monad-developers/ultrafuzz#710 · 1 comment ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
monad-developers/ultrafuzz#1110 ·
-
deferred-post-v0.1 enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
monad-developers/ultrafuzz#1108 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
monad-developers/ultrafuzz#1102 · 1 comment ·
All issues in monad-developers/ultrafuzz
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100