You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jobs@airflow.apache.org by GitBox <gi...@apache.org> on 2026/08/05 13:43:55 UTC

[GH] (airflow/cherry-pick-71171-v3-3-test): Workflow run "Tests (AMD)" is working again!

The GitHub Actions job "Tests (AMD)" on airflow.git/cherry-pick-71171-v3-3-test has succeeded.
Run started by GitHub user vatsrahul1001 (triggered by vatsrahul1001).

Head commit for run:
9a2a7433f800f5c73cdea0bd0b8158304d39a19e / Jarek Potiuk <ja...@potiuk.com>
Refresh the image registry cache in a workflow that cannot be cancelled (#71171)

* Refresh the image registry cache in a workflow that cannot be cancelled

A branch built on push refreshed its registry cache from inside the CI run, which
cancels in progress on the next push. With no cache the build runs cold, which widens
the window the next push cancels in, which leaves the cache missing -- v3-3-test held
only the default Python version's amd64 cache because that was the one matrix entry
that finished in time.

The refresh also has to cover every Python version: a version with no cache entry
builds from scratch on every run, and selective checks narrows the list on a text-only
push.

* Refresh constraints from a workflow of its own, covering every flavour

The manual constraints refresh shared a workflow with the automatic uv.lock push, so it
was filtered by that workflow's paths and buried under its name in the Actions list.

The documented procedures pointed at local builds -- refresh_images.sh for the image
cache, breeze commands for the constraints -- which need a buildx/qemu setup, a
committer login to ghcr.io, and enough bandwidth to push the layers. The workflows need
none of that, and unlike a local run they always cover every Python version and every
constraint flavour.

* Exempt a manually started cache refresh from the push cancellation

A push-triggered refresh should give way to the next one -- it is building the cache of a
commit that is no longer the tip. A manual run should not: it is started because the
branch has no cache and the push runs are the thing that keeps getting cancelled.

(cherry picked from commit e69c1881b32c36abb827bae3717eaf46424427bd)

Report URL: https://github.com/apache/airflow/actions/runs/31005062541

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: jobs-unsubscribe@airflow.apache.org
For additional commands, e-mail: jobs-help@airflow.apache.org