The Windows CI job on #1329 timed out while running litebox_runner_windows_userland::run::run_multithreaded_pe, despite the PR changing only litebox_platform_linux_userland/src/lib.rs.
In the failed job, 634 of 635 tests passed before run_multithreaded_pe hung after launching litebox-broker-userland.exe. Nextest terminated it at the 600-second timeout without additional stdout or stderr indicating the blocking operation.
The failed-job rerun passed without code changes: run_multithreaded_pe completed in 6.474 seconds, and all 635 tests completed in 70.511 seconds. This suggests a timing-dependent hang or lost-progress condition in the multithreaded Windows runner path.
The test should complete reliably or fail with diagnostics that identify which broker, runner, or guest thread is blocked.
The Windows CI job on #1329 timed out while running
litebox_runner_windows_userland::run::run_multithreaded_pe, despite the PR changing onlylitebox_platform_linux_userland/src/lib.rs.In the failed job, 634 of 635 tests passed before
run_multithreaded_pehung after launchinglitebox-broker-userland.exe. Nextest terminated it at the 600-second timeout without additional stdout or stderr indicating the blocking operation.The failed-job rerun passed without code changes:
run_multithreaded_pecompleted in 6.474 seconds, and all 635 tests completed in 70.511 seconds. This suggests a timing-dependent hang or lost-progress condition in the multithreaded Windows runner path.The test should complete reliably or fail with diagnostics that identify which broker, runner, or guest thread is blocked.