"Kelly's gripe seems justified, as the bug discussed in the thread appears to have popped up following a code change in February 2022 that users flagged in prior bug reports. The code change replaced instances of the posix "sleep" command with a "safe_sleep" script that failed to work as advertised. It was supposed to allow the GitHub Actions runner - the application that runs a job from a GitHub Actions workflow - to pause execution safely."
"After the CEO of GitHub said to 'embrace AI or get out', it seems the lackeys at Microsoft took the hint, because GitHub Actions started 'vibe-scheduling' - choosing jobs to run seemingly at random. Combined with other bugs and inability to manually intervene, this causes our CI system to get so backed up that not even master branch commits get checked."
The Zig Software Foundation moved its project from GitHub to Codeberg, alleging a decline in engineering quality and unreliable GitHub Actions. A thread titled "safe_sleep.sh rarely hangs indefinitely" began in April 2025; GitHub fixed the issue in August but the thread remained open. The underlying bug traces to a February 2022 change that replaced posix "sleep" with a "safe_sleep" script that could fail, sometimes consuming 100 percent CPU and running indefinitely. The move cites Actions' apparent "vibe-scheduling," inability to manually intervene, and resulting CI backlog that prevents timely checking of master-branch commits.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]