Repository navigation
ci: raise the test timeout 50m -> 90m - #623
Merged
Merged
Conversation
The windows lane of #618 died with `panic: test timed out after 50m0s`. The dump says the budget ran out rather than something hanging: the test listed as running had been running for 0s, and the binary's own total was 3007.445s — 50.1 minutes, a few seconds past the alarm. The three OS lanes run the full suite under -race with coverage, and windows is roughly twice the wall-clock of macOS and ubuntu. The vm suite grows with every conformance wave, so the margin that 50m left has been consumed. 90m restores it for several more. This is deliberately generous rather than exact: a timeout is a backstop against a hang, and the job-level budget (6h) is the real ceiling. Sizing it to just above today's runtime would mean revisiting it every wave, and each revisit is a red lane first. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Sep 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The windows lane of #618 died with
panic: test timed out after 50m0s.The dump says the budget ran out rather than something hanging:
The test listed as running had been running for 0s — it had just started — and the binary's own total was 3007.445s, which is 50.1 minutes. Nothing was stuck; the suite simply no longer fits.
The three OS lanes run the full suite under
-racewith coverage, and windows is roughly twice the wall-clock of macOS and ubuntu.internal/vmgrows with every conformance wave (this week alone: core/process 20→165 passing, language 1308→1443), so the margin 50m used to leave has been consumed.90m restores it for several waves. Deliberately generous rather than exact: a
-timeoutis a backstop against a hang, and the job-level budget (6h) is the real ceiling. Sizing it just above today's runtime would mean revisiting it every wave — and every revisit starts with a red lane and a false hang scare.🤖 Generated with Claude Code