Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -257,9 +257,13 @@ jobs:
if: ${{ needs.scope-gate.outputs.run-heavy == 'true' }}
runs-on: windows-latest
# Full-workspace `nextest archive` on hosted windows-latest has been
# dying at exactly 30m with no failed step. 45 leaves headroom for a
# cold cache without hiding a hung linker.
timeout-minutes: 45
# dying at the job timeout with no failed step: first at 30m, then at 45m
# (run 32789438873 burned 44m08s in `Build nextest archive` on a cold
# Swatinem cache -- the restore step took 12s, i.e. a miss -- and was
# killed mid-compile). Earlier runs only "finished" faster because a
# resolution error aborted the `tracedecay` lib-test unit early. 75m fits
# a genuinely cold cache while still failing loudly on a hung linker.
timeout-minutes: 75

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Fix the cold-cache build instead of raising its timeout

On a cold Windows cache, this patch only moves the cancellation ceiling from 45 to 75 minutes; the commit explicitly describes 75 minutes as an unobserved estimate, so the job can consume another 30 minutes and still cancel without establishing a passing Windows gate. Keep the existing ceiling and reduce, scope, or cache the Build nextest archive workload using measured cold-run evidence.

AGENTS.md reference: AGENTS.md:L126-L128

Useful? React with 👍 / 👎.

steps:
- uses: actions/checkout@v7

Expand Down
Loading