-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Only run ARM collection tests in main branch #45068
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
Conversation
The ARM collection tests are testing if all tests can be properly collected when packages not available on ARM are removed. We currently do not have such packages, but since this is only valid for providers and in version branches we never touch providers, we should just skip the test on non-main branch.
gopidesupavan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cool :)
Backport failed to create: v2-10-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker d1245cd v2-10-testThis should apply the commit to the v2-10-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
The ARM collection tests are testing if all tests can be properly collected when packages not available on ARM are removed. We currently do not have such packages, but since this is only valid for providers and in version branches we never touch providers, we should just skip the test on non-main branch. (cherry picked from commit d1245cd) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
The ARM collection tests are testing if all tests can be properly collected when packages not available on ARM are removed. We currently do not have such packages, but since this is only valid for providers and in version branches we never touch providers, we should just skip the test on non-main branch. (cherry picked from commit d1245cd) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
The ARM collection tests are testing if all tests can be properly collected when packages not available on ARM are removed. We currently do not have such packages, but since this is only valid for providers and in version branches we never touch providers, we should just skip the test on non-main branch. (cherry picked from commit d1245cd) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
…45076) The ARM collection tests are testing if all tests can be properly collected when packages not available on ARM are removed. We currently do not have such packages, but since this is only valid for providers and in version branches we never touch providers, we should just skip the test on non-main branch. (cherry picked from commit d1245cd)
The ARM collection tests are testing if all tests can be properly collected when packages not available on ARM are removed. We currently do not have such packages, but since this is only valid for providers and in version branches we never touch providers, we should just skip the test on non-main branch.
The ARM collection tests are testing if all tests can be properly collected when packages not available on ARM are removed. We currently do not have such packages, but since this is only valid for providers and in version branches we never touch providers, we should just skip the test on non-main branch. (cherry picked from commit d1245cd) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
The ARM collection tests are testing if all tests can be properly collected when packages not available on ARM are removed. We currently do not have such packages, but since this is only valid for providers and in version branches we never touch providers, we should just skip the test on non-main branch. (cherry picked from commit d1245cd) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
The ARM collection tests are testing if all tests can be properly collected when packages not available on ARM are removed. We currently do not have such packages, but since this is only valid for providers and in version branches we never touch providers, we should just skip the test on non-main branch.
^ 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.