Description
Since this week I experience stalling issues in my MacOS 26 x86_64 CI builds.
The workflow run seems to stall (hang) in some point of a compilation (C++) step (randomly is seems) and the workflow run gets terminated automatically after about an hour without any apparent errors.
Platforms affected
Runner images affected
Image version and build link
https://github.com/mcorino/wxRuby3/actions/runs/23909672830/job/69739799909
https://github.com/mcorino/wxRuby3/actions/runs/23922122359/job/69818505945
Is it regression?
Unknown. Did not ever see this problem before this week.
Expected behavior
The workflow run to finish normally, with or without errors.
Actual behavior
Workflow run seems to stall (hang) at random points in C++ compilation steps and gets terminated automatically with this notice:
"The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error."
There is however no CPU or Memory starving action at that point in the workflow as far as I know.
Repro steps
Run the MacOS workflows.
Description
Since this week I experience stalling issues in my MacOS 26 x86_64 CI builds.
The workflow run seems to stall (hang) in some point of a compilation (C++) step (randomly is seems) and the workflow run gets terminated automatically after about an hour without any apparent errors.
Platforms affected
Runner images affected
Image version and build link
https://github.com/mcorino/wxRuby3/actions/runs/23909672830/job/69739799909
https://github.com/mcorino/wxRuby3/actions/runs/23922122359/job/69818505945
Is it regression?
Unknown. Did not ever see this problem before this week.
Expected behavior
The workflow run to finish normally, with or without errors.
Actual behavior
Workflow run seems to stall (hang) at random points in C++ compilation steps and gets terminated automatically with this notice:
"The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error."
There is however no CPU or Memory starving action at that point in the workflow as far as I know.
Repro steps
Run the MacOS workflows.