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
It seems to be impossible to finish a CI test run. At least one of the jobs will fail with:
Error: Process completed with exit code 143.
A bit of research seems to indicate that this is Github Actions killing the runner, presumably due to hitting some resource limit. However, I wasn't able to find a solution.
This seems to be a problem again. Not every time, but most CI runs are failing because one task or another is being killed with:
Error: Process completed with exit code 143.
It's making CI only marginally useful.
We are already running with -parallel=1. The only thing I can think of to make it less resource intensive is to remove the race detector. But that has been valuable in the past. 🤷
Activity
Disable parallel testing on Github Actions CI
Disable parallel testing on Github Actions CI
jackc commentedon May 31, 2026
This seems to be a problem again. Not every time, but most CI runs are failing because one task or another is being killed with:
Error: Process completed with exit code 143.It's making CI only marginally useful.
We are already running with
-parallel=1. The only thing I can think of to make it less resource intensive is to remove the race detector. But that has been valuable in the past. 🤷[-]Github Actions CI is broken[/-][+]Github Actions CI is unreliable[/+]yavorl commentedon Aug 26, 2026
I began looking at this and noticed commit 93be536. It looks like it resolves it, no ci failures since then.
jackc commentedon Aug 28, 2026
Yes. I think that fixed it. I forgot to close the issue.