Skip to content

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented Dec 19, 2024

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.rst or {issue_number}.significant.rst, in newsfragments.

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.
Copy link
Member

@gopidesupavan gopidesupavan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cool :)

@potiuk potiuk merged commit d1245cd into apache:main Dec 19, 2024
98 checks passed
@potiuk potiuk deleted the only-run-arm-collection-in-main branch December 19, 2024 10:07
@github-actions
Copy link

Backport failed to create: v2-10-test. View the failure log Run details

Status Branch Result
v2-10-test Commit Link

You can attempt to backport this manually by running:

cherry_picker d1245cd v2-10-test

This should apply the commit to the v2-10-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

potiuk added a commit to potiuk/airflow that referenced this pull request Dec 19, 2024
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>
potiuk added a commit to potiuk/airflow that referenced this pull request Dec 19, 2024
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>
potiuk added a commit to potiuk/airflow that referenced this pull request Dec 19, 2024
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>
potiuk added a commit that referenced this pull request Dec 19, 2024
…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)
got686-yandex pushed a commit to got686-yandex/airflow that referenced this pull request Jan 30, 2025
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.
potiuk added a commit to potiuk/airflow that referenced this pull request Feb 17, 2025
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>
potiuk added a commit to potiuk/airflow that referenced this pull request Feb 17, 2025
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants