Consider avoiding the dependency on quay.io server in the GitHub Action "Check if generated files are up to date" job

[vstinner]

Last weeks/months, the quay.io server failed time time time. The problem is that the Python workflow has a GitHub Action "Check if generated files are up to date" job which pulls a container image from quay.io to run the make regen-configure command.

Should we consider avoiding the dependency on the quay.io server to make our workflow more reliable?

Linked PRs

• gh-112088: Run autoreconf in GHA check_generated_files #112090
• [3.12] gh-112088: Run autoreconf in GHA check_generated_files (GH-112090) #112126
• [3.12] gh-112088: Run autoreconf in GHA check_generated_files (GH-112090) #112159

[vstinner]

Recently, I documented commands to run make regen-configure with no container: https://docs.python.org/dev/using/configure.html#generated-files

I tried to run autoreconf -ivf -Werror in an Ubuntu 22.04 container (same Ubuntu version than the one currently used by the GHA job) to see if we can get the exact output. Sadly, it changes the output :-(

On Fedora, I create an Ubuntu 22.04 container with:

podman image pull ubuntu:22.04
podman image list --all
podman run --name ubuntu-dev --hostname ubuntu-dev --interactive --tty ubuntu:22.04

Commands which are supposed to produce the same output than make regen-configure:

apt update
apt install -y git autotools-dev autoconf autoconf-archive pkgconf
git clone https://github.com/python/cpython/ --depth=1
cd cpython/
autoreconf -ivf -Werror
git diff

Output:

diff --git a/aclocal.m4 b/aclocal.m4
index da8ee95..b309f4d 100644
--- a/aclocal.m4
+++ b/aclocal.m4
@@ -1,4 +1,4 @@
-# generated automatically by aclocal 1.16.4 -*- Autoconf -*-
+# generated automatically by aclocal 1.16.5 -*- Autoconf -*-
 
 # Copyright (C) 1996-2021 Free Software Foundation, Inc.
 

Versions retrieved by dpkg -l|grep -E 'autotools|autoconf|pkgconf':

• autoconf 2.71-2
• autoconf-archive 20210219-2.1
• autotools-dev 20220109.1
• libpkgconf3:amd64 1.8.0-1
• pkgconf 1.8.0-1

[vstinner]

cc @erlend-aasland

[vstinner]

Last weeks/months, the quay.io server failed time time time.

Example:

Trying to pull quay.io/tiran/cpython_autoconf:271...
Error: initializing source docker://quay.io/tiran/cpython_autoconf:271: reading manifest 271 in quay.io/tiran/cpython_autoconf: received unexpected HTTP status: 504 Gateway Time-out

build: https://github.com/python/cpython/actions/runs/6869118007/job/18682243065?pr=112063

[vstinner]

This latest server issue is tracked at: https://status.quay.io/incidents/z7sbjqmb34p1

[vstinner]

The server fails with different errors:

podman run --rm --pull=always -v /home/runner/work/cpython/cpython:/src quay.io/tiran/cpython_autoconf:271
Trying to pull quay.io/tiran/cpython_autoconf:271...
Error: initializing source docker://quay.io/tiran/cpython_autoconf:271: can't talk to a V1 container registry

[vstinner]

apt install -y git autotools-dev autoconf autoconf-archive pkgconf

Hum, pkg-config should be installed, not pkgconf.

[vstinner]

This latest server issue is tracked at: https://status.quay.io/incidents/z7sbjqmb34p1

Recent https://status.quay.io/ events:

• Nov 5, 2023: Production database maintenance
• Nov 8, 2023: Quay.io is experiencing an outage
• Nov 9, 2023: Quay.io is experiencing an outage
• Nov 12, 2023: Quay.io Database maintenance
• Nov 12, 2023: Quay.io moving to read-only mode
• Nov 14, 2023: Unresolved incident: Sporadic image pull failures