Skip to content

Ubuntu freethreading build failed twice spuriously #150139

Closed as duplicate
Closed as duplicate

Description

@jaraco

While attempting to complete #134264, I had to retry the failed jobs 3 times (4 attempts) to get success. The first failure was in the "content from changed files" job. The two subsequent failures were in Ubuntu freethreading.

Can these checks be made more robust?

Originally posted by @jaraco in #134264 (comment)

Activity

  1. hugovk commented on May 20, 2026

    @hugovk
    Member

    The free-threading one sounds like it's been fixed by #150115; update from main to pull it in for other PRs.

    Please can you link to the logs for the other one?

  2. StanFromIreland commented on May 20, 2026

    @StanFromIreland
    Member

    The content one was probably the Git bug I noted in the Discord, the others sound like #150114

  3. jaraco commented on May 20, 2026

    @jaraco
    MemberAuthor

    Here's the build that failed with content from changed files: https://github.com/python/cpython/actions/runs/26120565421/job/76821272700

    + git fetch origin +0f962dc8601f31d7b9e1be6745a7cf7c4d5ef94e:remotes/origin/main --depth=10 --no-tags --prune --no-recurse-submodules
    From https://github.com/python/cpython
     * [new ref]         0f962dc8601f31d7b9e1be6745a7cf7c4d5ef94e -> origin/main
    ++ git rev-list --first-parent --max-parents=0 --max-count=1 origin/main
    + COMMON_ANCESTOR=9983c7d4416cac8deb2fded1ec9c7daf786c3a02
    ++ git log --date=iso8601 --format=%cd 9983c7d4416cac8deb2fded1ec9c7daf786c3a02
    + DATE='2025-05-18 22:21:06 +0300'
    + git fetch origin +51a5715df9c56f616944cf1b39323bd6ae009143:remotes/origin/main '--shallow-since=2025-05-18 22:21:06 +0300' --no-tags --prune --no-recurse-submodules
    fatal: shallow file has changed since we read it
    Error: Process completed with exit code 128.
    
  4. StanFromIreland commented on May 20, 2026

    @StanFromIreland
    Member

    Yep that's it. Is the other issue resolved, in that case we can close as a duplicate of the other issue?

  5. jaraco commented on May 20, 2026

    @jaraco
    MemberAuthor

    I suspect it is resolved. I won't know if it's resolved until I run a build again, but I agree, let's close this as duplicate.

  6. reopened this on May 20, 2026
  7. jaraco commented on May 20, 2026

    @jaraco
    MemberAuthor

    The content one was probably the Git bug I noted in the Discord, the others sound like #150114

    Here's the discord message, and the linked upstream 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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions