Github Actions CI is broken #1934
Comments
jackc
added a commit
that referenced
this issue
Mar 16, 2024
Tests were failing with: Error: Process completed with exit code 143. This appears to mean that Github Actions killed the runner. See https://github.com/jackc/pgx/actions/runs/8216337993/job/22470808811 for an example. It appears Github Actions kills runners based on resource usage. Running tests one at a time reduces the resource usage and avoids the problem. Or at least that's what I presume is happening. It sure is fun debugging issues on cloud systems where you have limited visibility... :( fixes #1934
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: