Skip to content
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

Skip example importability tests for providers in non-main branches #43260

Conversation

potiuk
Copy link
Member

@potiuk potiuk commented Oct 22, 2024

When "Always" tests are running in v2* branches, they also tested provider examples for importability. However sometimes those tests failed because we have not cherry-picked some of the provider's changes that were necessary for the examples to get imported.

This PR excludes provider's examples from the "always" running importability tests, when the branch we are running it in is not main (i.e. we are in one of the past v2-branches).


^ 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.

When "Always" tests are running in v2* branches, they also tested
provider examples for importability. However sometimes those tests
failed because we have not cherry-picked some of the provider's
changes that were necessary for the examples to get imported.

This PR excludes provider's examples from the "always" running
importability tests, when the branch we are running it in is
not main (i.e. we are in one of the past v2-branches).
@potiuk potiuk added this to the Airflow 2.10.3 milestone Oct 22, 2024
@potiuk potiuk merged commit 0f38be1 into apache:main Oct 22, 2024
49 checks passed
@potiuk potiuk deleted the skip-importing-providers-examples-in-non-main-branches branch October 22, 2024 12:06
potiuk added a commit to potiuk/airflow that referenced this pull request Oct 22, 2024
…pache#43260)

When "Always" tests are running in v2* branches, they also tested
provider examples for importability. However sometimes those tests
failed because we have not cherry-picked some of the provider's
changes that were necessary for the examples to get imported.

This PR excludes provider's examples from the "always" running
importability tests, when the branch we are running it in is
not main (i.e. we are in one of the past v2-branches).

(cherry picked from commit 0f38be1)
potiuk added a commit to potiuk/airflow that referenced this pull request Oct 22, 2024
While the apache#43260 attempted to address the problem where example
dag importability tests should skip provider tests on non-main,
it did not actually solve the problem.

While debugging it, it turned out that since apache#42505, the provider
tests were not executed in main "at all" - the "providers"
directory was not included in the list of places to check for
the example dags (they were in "airflow" in v2-10-test") this is
why it "looked like" the solution worked in "main".

This PR fixes both problems:

* brings back importability of provider's example_dags in main branch
* properly excludes the providers examples in non-main branch
potiuk added a commit that referenced this pull request Oct 22, 2024
…43260) (#43263)

When "Always" tests are running in v2* branches, they also tested
provider examples for importability. However sometimes those tests
failed because we have not cherry-picked some of the provider's
changes that were necessary for the examples to get imported.

This PR excludes provider's examples from the "always" running
importability tests, when the branch we are running it in is
not main (i.e. we are in one of the past v2-branches).

(cherry picked from commit 0f38be1)
potiuk added a commit that referenced this pull request Oct 23, 2024
While the #43260 attempted to address the problem where example
dag importability tests should skip provider tests on non-main,
it did not actually solve the problem.

While debugging it, it turned out that since #42505, the provider
tests were not executed in main "at all" - the "providers"
directory was not included in the list of places to check for
the example dags (they were in "airflow" in v2-10-test") this is
why it "looked like" the solution worked in "main".

This PR fixes both problems:

* brings back importability of provider's example_dags in main branch
* properly excludes the providers examples in non-main branch
potiuk added a commit to potiuk/airflow that referenced this pull request Oct 23, 2024
…43273)

While the apache#43260 attempted to address the problem where example
dag importability tests should skip provider tests on non-main,
it did not actually solve the problem.

While debugging it, it turned out that since apache#42505, the provider
tests were not executed in main "at all" - the "providers"
directory was not included in the list of places to check for
the example dags (they were in "airflow" in v2-10-test") this is
why it "looked like" the solution worked in "main".

This PR fixes both problems:

* brings back importability of provider's example_dags in main branch
* properly excludes the providers examples in non-main branch
utkarsharma2 pushed a commit that referenced this pull request Oct 23, 2024
…43260) (#43263)

When "Always" tests are running in v2* branches, they also tested
provider examples for importability. However sometimes those tests
failed because we have not cherry-picked some of the provider's
changes that were necessary for the examples to get imported.

This PR excludes provider's examples from the "always" running
importability tests, when the branch we are running it in is
not main (i.e. we are in one of the past v2-branches).

(cherry picked from commit 0f38be1)
potiuk added a commit that referenced this pull request Oct 23, 2024
…#43307)

While the #43260 attempted to address the problem where example
dag importability tests should skip provider tests on non-main,
it did not actually solve the problem.

While debugging it, it turned out that since #42505, the provider
tests were not executed in main "at all" - the "providers"
directory was not included in the list of places to check for
the example dags (they were in "airflow" in v2-10-test") this is
why it "looked like" the solution worked in "main".

This PR fixes both problems:

* brings back importability of provider's example_dags in main branch
* properly excludes the providers examples in non-main branch
harjeevanmaan pushed a commit to harjeevanmaan/airflow that referenced this pull request Oct 23, 2024
…pache#43260)

When "Always" tests are running in v2* branches, they also tested
provider examples for importability. However sometimes those tests
failed because we have not cherry-picked some of the provider's
changes that were necessary for the examples to get imported.

This PR excludes provider's examples from the "always" running
importability tests, when the branch we are running it in is
not main (i.e. we are in one of the past v2-branches).
harjeevanmaan pushed a commit to harjeevanmaan/airflow that referenced this pull request Oct 23, 2024
…43273)

While the apache#43260 attempted to address the problem where example
dag importability tests should skip provider tests on non-main,
it did not actually solve the problem.

While debugging it, it turned out that since apache#42505, the provider
tests were not executed in main "at all" - the "providers"
directory was not included in the list of places to check for
the example dags (they were in "airflow" in v2-10-test") this is
why it "looked like" the solution worked in "main".

This PR fixes both problems:

* brings back importability of provider's example_dags in main branch
* properly excludes the providers examples in non-main branch
PaulKobow7536 pushed a commit to PaulKobow7536/airflow that referenced this pull request Oct 24, 2024
…pache#43260)

When "Always" tests are running in v2* branches, they also tested
provider examples for importability. However sometimes those tests
failed because we have not cherry-picked some of the provider's
changes that were necessary for the examples to get imported.

This PR excludes provider's examples from the "always" running
importability tests, when the branch we are running it in is
not main (i.e. we are in one of the past v2-branches).
PaulKobow7536 pushed a commit to PaulKobow7536/airflow that referenced this pull request Oct 24, 2024
…43273)

While the apache#43260 attempted to address the problem where example
dag importability tests should skip provider tests on non-main,
it did not actually solve the problem.

While debugging it, it turned out that since apache#42505, the provider
tests were not executed in main "at all" - the "providers"
directory was not included in the list of places to check for
the example dags (they were in "airflow" in v2-10-test") this is
why it "looked like" the solution worked in "main".

This PR fixes both problems:

* brings back importability of provider's example_dags in main branch
* properly excludes the providers examples in non-main branch
utkarsharma2 pushed a commit that referenced this pull request Oct 24, 2024
…43260) (#43263)

When "Always" tests are running in v2* branches, they also tested
provider examples for importability. However sometimes those tests
failed because we have not cherry-picked some of the provider's
changes that were necessary for the examples to get imported.

This PR excludes provider's examples from the "always" running
importability tests, when the branch we are running it in is
not main (i.e. we are in one of the past v2-branches).

(cherry picked from commit 0f38be1)
utkarsharma2 pushed a commit that referenced this pull request Oct 24, 2024
…#43307)

While the #43260 attempted to address the problem where example
dag importability tests should skip provider tests on non-main,
it did not actually solve the problem.

While debugging it, it turned out that since #42505, the provider
tests were not executed in main "at all" - the "providers"
directory was not included in the list of places to check for
the example dags (they were in "airflow" in v2-10-test") this is
why it "looked like" the solution worked in "main".

This PR fixes both problems:

* brings back importability of provider's example_dags in main branch
* properly excludes the providers examples in non-main branch
ellisms pushed a commit to ellisms/airflow that referenced this pull request Nov 13, 2024
…pache#43260)

When "Always" tests are running in v2* branches, they also tested
provider examples for importability. However sometimes those tests
failed because we have not cherry-picked some of the provider's
changes that were necessary for the examples to get imported.

This PR excludes provider's examples from the "always" running
importability tests, when the branch we are running it in is
not main (i.e. we are in one of the past v2-branches).
ellisms pushed a commit to ellisms/airflow that referenced this pull request Nov 13, 2024
…43273)

While the apache#43260 attempted to address the problem where example
dag importability tests should skip provider tests on non-main,
it did not actually solve the problem.

While debugging it, it turned out that since apache#42505, the provider
tests were not executed in main "at all" - the "providers"
directory was not included in the list of places to check for
the example dags (they were in "airflow" in v2-10-test") this is
why it "looked like" the solution worked in "main".

This PR fixes both problems:

* brings back importability of provider's example_dags in main branch
* properly excludes the providers examples in non-main branch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants