-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
Run tests for Providers also for Airflow 2.8 #39606
Run tests for Providers also for Airflow 2.8 #39606
Conversation
9b729bf
to
4cf22f9
Compare
4cf22f9
to
a61412e
Compare
OK. Just 4 tests left to fix in 2.8 :). |
e1b9f59
to
3fb63e3
Compare
dced766
to
f778dd7
Compare
81a7e35
to
d05e641
Compare
I was wondering why i could not do it. I was trying to run breeze with dev providers and Airflow 2.8.4 like you mentioned, but the fab provider required 2.9.0. After i dealt with it, and run the test, it passed without any problems, but now it makes more sense. Anyway, glad that it should be solved now ^^ |
Yes. I have to upgrade the docs to add information about removing incompatible providers (and I think I can change it to run those tests locally without actually building packages - so that will simplify the process (separate PR) |
OK . That one is ready to be finally reviewed. All problems with compatibility with 2.8 have been solved in the test suite, also thanks to that one we found out the compatbility issue of common.io filetransfer openlineage integration for 2.8 that has been fixed in #39755 -> so thsoe tests are alredy showing it's worth 🚀 Once this one is merged, I will work on 2.7 compatibility and - in parallell - making it easier to debug and reproduce the tests with previous version of airflow locally. |
7adad37
to
9989b43
Compare
I would love to merge that one and work on 2.7 tests :) |
58fc9ea
to
b04b658
Compare
Anyone :) ? I am already working on 2.7 compatibility in #39862 |
b04b658
to
59a3836
Compare
This is a follow-up on apache#39513 to add support for running Provider tests against Airlfow 2.8 installed from PyPI. This change includes: * simplifying the way how we specify provider exclusions in tests * update to the unit test documentation describing testing * updating to latest pytest tooling in case older airflow version is installed (pulling the correct versions and correct packages for pytest extensions) * implementing 2.8 compatibility for the conftest/test common code * implementing 2.8 compatibility for provider tests that relied on 2.9+ behaviours
59a3836
to
e30cdf9
Compare
This is a follow-up on apache#39513 to add support for running Provider tests against Airlfow 2.8 installed from PyPI. This change includes: * simplifying the way how we specify provider exclusions in tests * update to the unit test documentation describing testing * updating to latest pytest tooling in case older airflow version is installed (pulling the correct versions and correct packages for pytest extensions) * implementing 2.8 compatibility for the conftest/test common code * implementing 2.8 compatibility for provider tests that relied on 2.9+ behaviours
This is a follow-up on apache#39513 to add support for running Provider tests against Airlfow 2.8 installed from PyPI. This change includes: * simplifying the way how we specify provider exclusions in tests * update to the unit test documentation describing testing * updating to latest pytest tooling in case older airflow version is installed (pulling the correct versions and correct packages for pytest extensions) * implementing 2.8 compatibility for the conftest/test common code * implementing 2.8 compatibility for provider tests that relied on 2.9+ behaviours
This is a follow-up on #39513 to add support for running Provider
tests against Airlfow 2.8 installed from PyPI.
^ 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.rst
or{issue_number}.significant.rst
, in newsfragments.