You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
CI: PublishTestProjectAOTModule intermittently hangs for 30 minutes on macOS #7211
On the modularpipeline (macos-latest) job, PublishTestProjectAOTModule sometimes runs until the 30-minute module timeout and is then killed:
PublishTestProjectAOTModule ✗ (30.0m) - ModuleTimeoutException
ModuleTimeoutException: PublishTestProjectAOTModule has timed out after 30m & 0s. The module did not respond to the cancellation token and was forcibly ...
The same module normally finishes in about 1.8 minutes on macOS, so this is a hang, not a slow publish. Seen on 2026-10-20 on three unrelated PRs:
tools/TUnit.Pipeline/Modules/PublishTestProjectAOTModule.cs, which runs dotnet publish with Aot=true for TUnit.TestProject (net10.0) into artifacts/aot-publish.
Expected
The publish either completes or fails fast. Worth checking:
whether the native linker / ILCompiler step stalls under the parallel load of other modules on the macOS runner (memory pressure);
adding ShowStandardOutput or a heartbeat so the hang point is visible in logs;
whether dotnet publish should get --disable-build-servers or a lower ILC parallelism on macOS;
whether the module should honour cancellation so the job fails at the timeout instead of being force-killed.
Reproduce
Intermittent on GitHub-hosted macos-latest runners during a busy queue.
Closing: the cause is fixed on main. These were not hangs. After #7131 the AOT publish competed with the test modules on the 3-core macOS runner and took 24–27 minutes even on passing runs. #7216 raised the module timeout to 60 minutes, and #7226 moved the AOT publish into its own aot.yml workflow, so it no longer competes with the test modules.
Evidence: of the last 60 aot.yml runs, 46 succeeded, 5 were cancelled and 2 failed. Neither failure was a timeout: every failed job finished in 4–8 minutes (runs 41307113428 and 41201223625). Reopen this if a ModuleTimeoutException shows up again.
Activity
thomhurst commentedon Oct 20, 2026
Seen again on PR #7180 macOS (job 118476810599).
thomhurst commentedon Oct 20, 2026
Seen again on PR #7144 macOS (job 118485945080). Fifth occurrence on 2026-10-20.
thomhurst commentedon Nov 1, 2026
Closing: the cause is fixed on
main. These were not hangs. After #7131 the AOT publish competed with the test modules on the 3-core macOS runner and took 24–27 minutes even on passing runs. #7216 raised the module timeout to 60 minutes, and #7226 moved the AOT publish into its ownaot.ymlworkflow, so it no longer competes with the test modules.Evidence: of the last 60
aot.ymlruns, 46 succeeded, 5 were cancelled and 2 failed. Neither failure was a timeout: every failed job finished in 4–8 minutes (runs 41307113428 and 41201223625). Reopen this if aModuleTimeoutExceptionshows up again.