The GitHub Actions job "Tests (AMD)" on airflow.git/seed-ci-image-cache-from-stashed-image has failed. Run started by GitHub user potiuk (triggered by potiuk).
Head commit for run: 58b4fad0e37985cab71d00a7b08b16067cdbfdaf / Jarek Potiuk <[email protected]> Speed up docs publishes by reusing the previously built CI image Publishing docs for a ref cut before main pays for a from-scratch CI image build. The registry cache the build reads is main's, and the first Dockerfile.ci change made since the ref was cut breaks the cache chain at the third layer - #70285, which bakes Node.js and pnpm into the image, is by itself enough to make the twenty-minute Python build run again. Nothing caches those layers for the ref being documented except the image the previous publish of that same ref already built. That image could not serve as a cache until now. BuildKit imports the cache manifest of an image loaded from a tarball and then discards every record whose layers it cannot pull from a registry, so a docker load contributes nothing at all; serving the image from a registry on localhost is what makes its records usable. Recording those records in the first place needs inline cache metadata, which no image carried before. Report URL: https://github.com/apache/airflow/actions/runs/30405595779 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
