Repository navigation
ci: cap the job and name tests that hang - #3
Merged
Merged
Conversation
Every run has stalled in Build and test until GitHub cancelled it at 6 hours, with no log showing why. Limit the job to 20 minutes and use blame-hang so a stuck test is killed after 5 minutes and identified in the output. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Summary
Every CI run has stalled in
Build and testuntil GitHub cancelled it at the 6-hour limit, and the cancelled runs leave no usable log. This caps the job and makes a hang name the test responsible.Changes
timeout-minutes: 20on the job.dotnet testruns with--blame-hang --blame-hang-timeout 5m, which kills a stuck test and reports it. No dump is collected.Expected result
This PR may well fail. That's useful: it should fail in minutes and name the test, replacing a silent 6-hour cancel.
The likely cause is the
Phase1*Gatetests, which launch real desktop apps with no guard for a headless runner. That's unconfirmed, so this PR doesn't exclude any tests.🤖 Generated with Claude Code