topherinternational commented on PR #41555: URL: https://github.com/apache/airflow/pull/41555#issuecomment-2306136496
@potiuk @eladkal we have 3 persistent failures in the provider checks; tldr, I think there's a bug-ish in the provider checks commands in breeze where all providers are assumed to be supported on Python 3.8. The command `breeze release-management verify-provider-packages --use-packages-from-dist --package-format wheel --use-airflow-version wheel --airflow-constraints-reference default --providers-constraints-location /files/constraints-3.8/constraints-source-providers-3.8.txt` installs all of the provider wheels built in the earlier `breeze release-management prepare-provider-packages ...` step. This process all runs on 3.8 and so implicitly assumes that all of the providers are legit for 3.8; neither step looks like it checks `excluded-python-versions`. So the install fails due to the ibmcloudant and snowflake dependency conflict (the very reason we excluded 3.8 in the first place). These commands happen in `Provider packages wheel build and verify`, `Compat 2.8.4:P3.8 provider check` and `Compat 2.9.1:P3.8 provider check`. Addressing this is obviously your call, but maybe some options are?: 1. Make `prepare-provider-packages` check excluded versions before building a particular provider wheel 2. Add "Remove incompatible <version> provider packages" task to `Provider packages wheel build and verify`, and have the task reference the provider dependencies json and the excluded python versions. 3. Run the provider checks on every supported python version (after doing 1 or 2) I checked the repo and none of the released providers exclude Python 3.8, I figure maybe this problem hasn't come up yet. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
