aj 67fb80e660 ci: kill and name hung Windows tests instead of holding the runner ...

The first windows-desktop run hung for 25 minutes with no output and
ran until it was cancelled. Pass --blame-hang-timeout 5m so a test that
is silent for five minutes is killed, named in the log and mini-dumped
into TestResults, then cap the job at 20 minutes and upload all of
TestResults, not just the TRX files.

Checked locally with a throwaway xunit project: a Thread.Sleep(Infinite)
test was killed after the configured inactivity, named in the output,
and left a TRX, a test-order (Sequence) file and a mini dump; dotnet test
exited 1.

2026-10-04 18:39:08 -04:00

..

workflows

ci: kill and name hung Windows tests instead of holding the runner

2026-10-04 18:39:08 -04:00