The GitHub Actions job "Tests" on airflow.git has failed.
Run started by GitHub user potiuk (triggered by potiuk).

Head commit for run:
195bee381eb15e49a31c3fb8a44adb5b35a3ef2e / Jarek Potiuk <[email protected]>
Separate cache build to a separate workflow called from the main ci.yml

This is another step of decomposing our workflows and introducing
more DRY approach for GitHub Actions workflows we have. Building cache
started to take more time and space as we started to build 5 images
at the same time with Python 3.12 inclusion, so optimizing the builds
now is a good idea.

There are several optimizations here:

1) Instead of building images in parallel on bigger instances, we
   rather choose to start small ARM instances with less CPUs but
   build one image per instance. This will make them generally
   faster with the same price (less contention) at the expense
   of using more AMD instances to drive them

2) However we also make sure to build both AMD and ARM cache at
   the same time in parallel - the AMD on the driving AMD instance and
   the ARM on the ARM instance. This will make the AMD instances also
   busy while ARM instance is building their images - and AMD instance
   will be finishing faster in general rather than waiting for all the
   5 images to complete.

In order to accomplish it we change the parallelism model when
the `--prepare-buildx-cache` command is used - instead of parallelising
with python versions we parallelise with the platforms, which allows
to run both AMD and ARM image in parallel.

This change also removes building ARM image in build-images step as it
is not really needed for anything - we already do such build in the
CI workflow and builing it again in "build images" workflow is
superfluous.

Builds on changes implemented in #37865 and #38057

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

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to