The GitHub Actions job "Tests (AMD)" on airflow.git/skip-docs-image-build-when-ref-unchanged has failed. Run started by GitHub user potiuk (triggered by potiuk).
Head commit for run: 84b86d3583574680878fae27e566b597a285a7ab / Jarek Potiuk <[email protected]> Skip the docs CI image build when that ref was already built Docs for a ref are published more than once - an RC, then the final docs after the vote - and the second publish rebuilds an image the first one already built from the very same commit. Seeding the build cache with that image, as #70650 does, still pays for a docker load, a registry push, a build that hits cache on every layer, an export and two multi-gigabyte stash uploads, none of which can produce anything the first publish did not already produce. Reusing the image outright rather than as a cache turns on knowing it was built from this commit. A ref does not say that: a branch documented twice moves between the two publishes, so its image is a good cache and a wrong answer. The commit each image is stashed with is what tells those apart, and it is stashed on its own so that deciding costs a few bytes rather than the image the decision may make unnecessary. Reusing it also means publishing nothing, which the shared per-branch stash could not support: it is written by every build on this branch, so whoever restores it next would get sources they never asked for. The ref's own stash is the one this run's docs and registry jobs now read, so a run with nothing to build leaves them reading what the previous publish left there. The mount cache moves with it for the same reason - it holds the dependency set the sources resolve to, and a ref's and the branch tip's are exactly what differ. Report URL: https://github.com/apache/airflow/actions/runs/30443750368 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
