Summary
The Build and Test workflow can spend more than 50 minutes in build (windows-latest, net9.0) when the first dotnet test run hits the repository TestSessionTimeout.
Observed
- The initial Windows/net9.0 run aborts at
TestSessionTimeout=1800000 with Failed: 0.
- The workflow treats the non-zero exit as possible flakiness and starts a second full-suite retry.
- The retry causes the job to continue well past the useful diagnostic point.
Expected
The workflow should avoid retrying deterministic test-session timeouts, and the Windows/net9.0 lane should have a CI shape that can complete or fail with useful diagnostics within the intended job budget.
Summary
The Build and Test workflow can spend more than 50 minutes in
build (windows-latest, net9.0)when the firstdotnet testrun hits the repositoryTestSessionTimeout.Observed
TestSessionTimeout=1800000withFailed: 0.Expected
The workflow should avoid retrying deterministic test-session timeouts, and the Windows/net9.0 lane should have a CI shape that can complete or fail with useful diagnostics within the intended job budget.