Skip to content

Github Actions CI is unreliable #1934

Closed

Description

@jackc

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.

Activity

  1. reopened this on May 31, 2026
  2. jackc commented on May 31, 2026

    @jackc
    OwnerAuthor

    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. 🤷

  3. pinned this issue on May 31, 2026
  4. changed the title [-]Github Actions CI is broken[/-] [+]Github Actions CI is unreliable[/+] on May 31, 2026
  5. yavorl commented on Aug 26, 2026

    @yavorl

    I began looking at this and noticed commit 93be536. It looks like it resolves it, no ci failures since then.

  6. jackc commented on Aug 28, 2026

    @jackc
    OwnerAuthor

    Yes. I think that fixed it. I forgot to close the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions