Uh oh!
There was an error while loading. Please reload this page.
Automate exclusion of providers in lowest-dependency tests - #41991
Conversation
d49157d to
6d5c9c3Comparepotiuk
commented
Sep 4, 2024
That one should also speed up "lowest dependencies" test in main - because we - erroneously excluded |
topherinternational
commented
Sep 4, 2024
I think the followup to #41967 I am writing will also address this problem. |
potiuk
commented
Sep 4, 2024
We can compare and choose better one :) |
0102e45 to
5ecbaafComparepotiuk
commented
Sep 4, 2024
Actually this one also solves "main" failures of Python 3.12 "Lowest dependencies" tests that I've seen recently! |
topherinternational
commented
Sep 4, 2024
Or we can have defense in depth :D |
63075e2 to
34917b0CompareThe "lowest" dependency tests had "hard-coded" exclusion for those providers that were excluded in specific python versions. This change automates it: * selective checks produce dictionary python -> excluded versions * the dictionary (as string) is passed to unit tests in actions * the dictionary (as string) is passed to breeze container as EXCLUDED_PROVIDERS variable * "is_provider_excluded.py" checks if the provider is excluded and exits with success if so Related: apache#41555
34917b0 to
52227f2Compare
The "lowest" dependency tests had "hard-coded" exclusion for those providers that were excluded in specific python versions.
This change automates it:
Related: #41555
^ 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.