-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix broken breeze by fixing packaging version #34701
Conversation
81cff00
to
68624d2
Compare
68624d2
to
62278ca
Compare
Is there log of a failing run? I think the new release has a bug. |
@uranusjr Not sure whether this is the log you're looking for. But these are the logs for my failing breeze run on ci, https://github.com/apache/airflow/actions/runs/6377228541/job/17305505217
on local
|
Hmm that doesn’t seem to be related to packaging. And it’s failing with the same error here too, so maybe there are two separate issues here. |
Some CI jobs load the scripts files from main ( airflow/.github/actions/get-target-branch-build-scripts/action.yml Lines 37 to 43 in 4c1808b
Tests / Build info , you see that the change fixes the issue in this job
|
So is neither of the errors above is related to what you’re trying to fix here? |
OK looks like this is the error
which is a consequence of pypa/pipx#1070 I’ve opened pypa/pipx#1071 to fix this so hopefully this will be resolved soon. Since the CI is broken by too many things now I’ll green light to merge this directly. |
I will merge to check if the main CI will be fixed. |
Looks like it works 🎉 |
The fix in pipx pypa/pipx#1071 also seems to work for me ( |
(cherry picked from commit 6618c5f)
@hussein-awala (and others) for the future - the way for committers to test such a PR is to make PR from "airflow" repo, not from a fork. Maintainers can push branches directly to That's this flow: https://github.com/apache/airflow/blob/main/CI_DIAGRAMS.md#pull-request-flow-from-apacheairflow-repo And for the record - this whole setup is done in order to achieve security - users from their fork should not be able to modify code that is run in "Github Actions" - because this code can be harmful and get access to GITHUB_TOKEN, write permissions and other sensitive data (secrets). This is also one of the requirements by the ASF to enable 'run workflows" automatically for forks for external contributors - otherwise we would have to manually approve every single workflow run. |
Had the same issue today on a fresh Fedora system, installing pipx via
Solution: Setting up pipx with |
Thank you @potiuk for the clarification, this is very interesting. I see the CI fails in #34775 although it cherry-pick this commit and source branch is in Apache repository, do you have any idea? |
Yes. We can ignore it. This failure can be ignored. "Pull request target" is run for all PRs but it does "nothing" when PR comes from the "apache" repository based on build info output (but in this case the 'build info" step is failing). As you can see there, all the tests are running and succeeding. Once merged, the build will succeed. |
The CI is broken in main, and comparing the different runs I noticed that the only difference is the version of
packaging
where there was a new version 7 hours ago (https://github.com/pypa/packaging/releases/tag/23.2).