Skip to content

ci: cap the job and name tests that hang - #3

Merged
synthet merged 1 commit into
mainfrom
ci/test-hang-timeout
Nov 4, 2026
Merged

synthet merged 1 commit into
mainfrom
ci/test-hang-timeout

Conversation

@synthet

@synthet synthet commented Nov 4, 2026

Copy link
Copy Markdown
Owner

Summary

Every CI run has stalled in Build and test until 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: 20 on the job.
  • dotnet test runs 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*Gate tests, 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

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>
@synthet
synthet merged commit 23357b5 into main Nov 4, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant