Skip to content

build: re-validate the pinned test jobs on Ubuntu 26.04 and remove the ubuntu-24.04 pins #903

Closed

Description

@jeffreyaven

GitHub moved ubuntu-latest to Ubuntu 26.04 on 2026-11-04. Three jobs in .github/workflows/build.yml were pinned to ubuntu-24.04 in #896 so the release could proceed; they should be re-validated on 26.04 and unpinned.

What failed on 26.04 (image ubuntu26/20261025.179):

  • Linux Test (test/registry): the nginx apt-key import aborts before any test runs, gpg: Fatal: /home/runner/.gnupg: directory does not exist! (gpg 2.4.8 no longer creates its home directory on first use). Likely fix: create ~/.gnupg with mode 700 before the import, or switch the nginx repository setup to a keyring file under /etc/apt/keyrings.
  • Docker Test amd64 shards and Docker Python Test: 33 exact-output robot assertions fail because the newer Docker Compose writes container progress lines into the output the mocked suite captures. Likely fix: --progress=quiet (or COMPOSE_PROGRESS=quiet) on the compose invocations in the test harness, or capturing only the container's stdout.
  • Docker Test Shard Verification was pinned alongside the shards.

The arm64 legs on ubuntu-24.04-arm were unaffected. Linux Build, Test Python Package Build and Docker Build passed on 26.04 and stay unpinned.

  • Fix the gpg homedir abort in the Linux Test setup.
  • Silence or filter Docker Compose progress output in the mocked robot runs.
  • Run the three jobs on ubuntu-latest on a branch and remove the pins (linuxtest, the dockertest amd64 leg, dockertestverify).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions