5f4ecabc8ac530b823c9dd0dfe77d0af241b4d89
The nightly (run #47) portable job failed CreateAsync_WhenFakeWorkerNeverSendsReady _TimesOutAndKillsWorker: it asserts the factory's TimeoutException carries 'did not complete startup' (thrown at the session's 1s startup timeout), but the test's .WaitAsync(TestTimeout=5s) anti-hang net tripped first under CI load and surfaced .NET's generic 'The operation has timed out.' — same commit passed on the push run (#46), so it's a load-sensitive timeout race, not a regression. Raising runner capacity to 4 makes concurrent-load flakes like this more likely. Fix: give the two CreateAsync failure/timeout tests a dedicated 30s HangGuardTimeout, far above the 1s semantic timeout under test, so the factory's own exception is always the one observed. The net still catches a genuine hang. Note: this class cannot run on macOS (named pipes -> Unix domain sockets fail on the pipe path); verification is via CI Linux.
Description
No description provided
Languages
Java
45.3%
C#
42.6%
Python
3.4%
Rust
3.3%
Go
2.6%
Other
2.7%