Change Paralell constraints generation to sequential #46223
Merged
Conversation
This file contains 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
Parallel constraint generation runs several docker containers and it produces some build artifacts in paralllel (when compiling spar) that are huge - when run in parallell we are runnig out of disk space for them. Changing to sequential execution hopefully shoudl fix it.
jedcunningham
approved these changes
Jan 29, 2025
got686-yandex
pushed a commit
to got686-yandex/airflow
that referenced
this pull request
Jan 30, 2025
Parallel constraint generation runs several docker containers and it produces some build artifacts in paralllel (when compiling spar) that are huge - when run in parallell we are runnig out of disk space for them. Changing to sequential execution hopefully shoudl fix it.
ambika-garg
pushed a commit
to ambika-garg/airflow
that referenced
this pull request
Jan 30, 2025
Parallel constraint generation runs several docker containers and it produces some build artifacts in paralllel (when compiling spar) that are huge - when run in parallell we are runnig out of disk space for them. Changing to sequential execution hopefully shoudl fix it.
niklasr22
pushed a commit
to niklasr22/airflow
that referenced
this pull request
Feb 8, 2025
Parallel constraint generation runs several docker containers and it produces some build artifacts in paralllel (when compiling spar) that are huge - when run in parallell we are runnig out of disk space for them. Changing to sequential execution hopefully shoudl fix it.
jedcunningham
added a commit
to astronomer/airflow
that referenced
this pull request
Feb 14, 2025
When we switched to sequential in apache#46223, we missed actually passing the python version. Oops.
potiuk
pushed a commit
that referenced
this pull request
Feb 14, 2025
When we switched to sequential in #46223, we missed actually passing the python version. Oops.
alecsg77
pushed a commit
to alecsg77/airflow
that referenced
this pull request
Feb 14, 2025
When we switched to sequential in apache#46223, we missed actually passing the python version. Oops.
ambika-garg
pushed a commit
to ambika-garg/airflow
that referenced
this pull request
Feb 17, 2025
Parallel constraint generation runs several docker containers and it produces some build artifacts in paralllel (when compiling spar) that are huge - when run in parallell we are runnig out of disk space for them. Changing to sequential execution hopefully shoudl fix it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Parallel constraint generation runs several docker containers and it produces some build artifacts in paralllel (when compiling spar) that are huge - when run in parallell we are runnig out of disk space for them. Changing to sequential execution hopefully shoudl fix it.
^ 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 newsfragments.