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

Head commit for run:
6d42ccec754e84a96e016bbc20e29c014003b1f4 / Jens Scheffler 
<[email protected]>
Bugfix/fix disk space issues in GitHub (#47816)

* Fix disk space issues on github runners (#46358)

* Triage disk space issues, DO NOT MERGE

* Triage disk space issues, DO NOT MERGE

* Triage disk space issues, DO NOT MERGE

* Triage disk space issues, DO NOT MERGE

* Triage disk space issues, DO NOT MERGE

* Triage disk space issues, DO NOT MERGE

* Triage disk space issues, DO NOT MERGE

* Move docker storage to second drive in general

* Cleanup debug and triaging stuff

* Exception of docker volume for constraints building

* Fix ownership of files that docker uses in mounted directories (#46428)

The #46358 moved docker to another mounted directory - but this
directory and all files in it are owned by host user. The directory
and all files inside should be owned by root in order to properly
reflect permissions of the files when building docker images.

The change is now simplified. Rather than passing mount directory
by variable and passing it through GitHub Actions, we hard-code
the location of docker in cleanup_docker.sh script - we also
incorporate changing ownership and showing disk space in the same
cleanup_docker.sh script and make sure that script is only called
in the "real" (not composite) actions at the beginning - right
after the repository is checked out - previously that script
was also called in composite actions and changing the repo to be
writeable was done AFTER cleanup_docker.sh - which would not
work as we want the /mnt directory to be still owned by the
host user, but the docker storage should be still owned by root.

---------

Co-authored-by: Jarek Potiuk <[email protected]>

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

With regards,
GitHub Actions via GitBox


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

Reply via email to