The GitHub Actions job "Tests" on airflow.git has succeeded. Run started by GitHub user potiuk (triggered by potiuk).
Head commit for run: 6a5ed98ec760fd0ede3415a25e8062b44d6f3d60 / Jarek Potiuk <[email protected]> Fix edge case with constraints conflicting with setup dependencies There was an edge case with race condition between merging the setup.py change to main and refreshing constraint causing a failure of PROD image building when the new setup.py had conflicting dependencies with the past constraints. This happened on Aug 28 with azure-mgmt-containerinstance which got upgrade to a new 8.0.0 version which was conflicting with previous setup.py: * azure-mgmt-containerinstance>=1.5.0,<2.0 to * azure-mgmt-containerinstance>=7.0.0,<9.0.0 The problem was that PROD builds used the constraints from main to build the image, because constraints were not produced in the CI builds for the same job (constraints wer only produced in the PR that had "upgrade to newer depedencies". The regular PR CI builds have a build-in protection against such edge case - they run with `--upgrade-on-failure` flag that causes the PRs to upgrade their constraints eagerly if they fail on constraints failure. This PR fixes the edge case by utilising the result of the flag --upgrade-on failure. After this PR, constraints will always be uploaded by CI jobs, not only when "upgrade to newer dependencies" PR is run. this means that when CI build falls back as result of `--upgrade-on-failure` the newly generated constraints are uploaded as artifacts and used by PROD image build. As a side-effect, every PR will produce the constraints used by that build as artifact. This is actually pretty good thing for diagnosis of dependency problems. Report URL: https://github.com/apache/airflow/actions/runs/6004235519 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
