The GitHub Actions job "Tests" on airflow.git has failed. Run started by GitHub user potiuk (triggered by potiuk).
Head commit for run: 6106414711d1f13bce3dfa5d5dadbe7a73939231 / Jarek Potiuk <[email protected]> Adjust limits when constructing devel dependencies When we are constructing devel dependencies, we should adjust the limits to account for some apache-airflow packages that are not yet released. The adjustment is to add ".*" after the version number when dependency is lower-bound. It's not explicitly mentioned in PEP 440 - it is only mentioned there that it works for equality, but since `>=` is also part of `equal` it also works there. Example is a common-sql package that might be limited to `>=1.1.0` in google provider as part of the change, but it might not yet be released as it is being released together with the package it is needed by. It does not impact our CI, because we are anyhow removing the packages after installing (we only care about dependencies of their) and we are using source version of providers - but having a limit coming from another provider will make `pip` resolver fail if we do not adjust the limits. For CI, we also need to adjust the version whenever in our providers we refer to other providers with >= install clause because `--pre` flag in `pip` only allows to install direct pre-release (and development) dependencies but it does not modify requirements of those package to also include pre-releases as transitive dependency. Also a bug was found that would prevent to generate the dependencies in case provider.yaml file only changed (bad specification of .pre-commit include) Report URL: https://github.com/apache/airflow/actions/runs/2753561546 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
