More diagnostics and more logical name for cleaning up the runner #50540
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When we are starting the runner on CI we are cleaning it up and preparing the /mnt directory to be used for all kind of disk storage we need during CI build. This is happening in the step that was named "cleanup docker" but it did more than that. The script and all references to it are renamed, also more diagnostics is printed just before we restore CI image from cache to see how much space we have available, because for some reason we seem to have problems with disk space there in some jobs
potiuk
force-pushed
the
add-more-diagnostic-and-review-cleanup-code
branch
from
ac486c5 to
f120808
Compare
potiuk
added
the
backport-to-v3-1-test
jedcunningham
approved these changes
May 13, 2025
kaxil
approved these changes
May 13, 2025
Backport failed to create: v3-0-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker 51a84ce v3-0-testThis should apply the commit to the v3-0-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
kaxil
pushed a commit
that referenced
this pull request
May 14, 2025
…0540) When we are starting the runner on CI we are cleaning it up and preparing the /mnt directory to be used for all kind of disk storage we need during CI build. This is happening in the step that was named "cleanup docker" but it did more than that. The script and all references to it are renamed, also more diagnostics is printed just before we restore CI image from cache to see how much space we have available, because for some reason we seem to have problems with disk space there in some jobs (cherry picked from commit 51a84ce)
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
May 14, 2025
…ache#50540) When we are starting the runner on CI we are cleaning it up and preparing the /mnt directory to be used for all kind of disk storage we need during CI build. This is happening in the step that was named "cleanup docker" but it did more than that. The script and all references to it are renamed, also more diagnostics is printed just before we restore CI image from cache to see how much space we have available, because for some reason we seem to have problems with disk space there in some jobs (cherry picked from commit 51a84ce)
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
May 14, 2025
…e runner (apache#50540) When we are starting the runner on CI we are cleaning it up and preparing the /mnt directory to be used for all kind of disk storage we need during CI build. This is happening in the step that was named "cleanup docker" but it did more than that. The script and all references to it are renamed, also more diagnostics is printed just before we restore CI image from cache to see how much space we have available, because for some reason we seem to have problems with disk space there in some jobs (cherry picked from commit 51a84ce) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
May 14, 2025
…e runner (apache#50540) When we are starting the runner on CI we are cleaning it up and preparing the /mnt directory to be used for all kind of disk storage we need during CI build. This is happening in the step that was named "cleanup docker" but it did more than that. The script and all references to it are renamed, also more diagnostics is printed just before we restore CI image from cache to see how much space we have available, because for some reason we seem to have problems with disk space there in some jobs (cherry picked from commit 51a84ce) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk
added a commit
that referenced
this pull request
May 14, 2025
…e runner (#50540) (#50610) When we are starting the runner on CI we are cleaning it up and preparing the /mnt directory to be used for all kind of disk storage we need during CI build. This is happening in the step that was named "cleanup docker" but it did more than that. The script and all references to it are renamed, also more diagnostics is printed just before we restore CI image from cache to see how much space we have available, because for some reason we seem to have problems with disk space there in some jobs (cherry picked from commit 51a84ce)
kaxil
pushed a commit
that referenced
this pull request
Jun 3, 2025
…0540) When we are starting the runner on CI we are cleaning it up and preparing the /mnt directory to be used for all kind of disk storage we need during CI build. This is happening in the step that was named "cleanup docker" but it did more than that. The script and all references to it are renamed, also more diagnostics is printed just before we restore CI image from cache to see how much space we have available, because for some reason we seem to have problems with disk space there in some jobs (cherry picked from commit 51a84ce)
kaxil
pushed a commit
that referenced
this pull request
Jun 3, 2025
…e runner (#50540) (#50610) When we are starting the runner on CI we are cleaning it up and preparing the /mnt directory to be used for all kind of disk storage we need during CI build. This is happening in the step that was named "cleanup docker" but it did more than that. The script and all references to it are renamed, also more diagnostics is printed just before we restore CI image from cache to see how much space we have available, because for some reason we seem to have problems with disk space there in some jobs (cherry picked from commit 51a84ce)
sanederchik
pushed a commit
to sanederchik/airflow
that referenced
this pull request
Jun 7, 2025
…ache#50540) When we are starting the runner on CI we are cleaning it up and preparing the /mnt directory to be used for all kind of disk storage we need during CI build. This is happening in the step that was named "cleanup docker" but it did more than that. The script and all references to it are renamed, also more diagnostics is printed just before we restore CI image from cache to see how much space we have available, because for some reason we seem to have problems with disk space there in some jobs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When we are starting the runner on CI we are cleaning it up and preparing the /mnt directory to be used for all kind of disk storage we need during CI build. This is happening in the step that was named "cleanup docker" but it did more than that.
The script and all references to it are renamed, also more diagnostics is printed just before we restore CI image from cache to see how much space we have available, because for some reason we seem to have problems with disk space there in some jobs
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.