Skip to content

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented May 5, 2025

Since we have ubintu22.04-arm public runners available, we should be able to run a set of parallel tests for ARM - this would make our ARM images move out of experimental phase.

We are not running "all" tests - only those that make sense to run on ARM for "production" quality.

MySQL tests have some timeouts and run longer on ARM, that's why we
do not run MySQL tests on ARM as well.

We can also get rid of the "ARM collection" test that was introduced
to test if just collection of tests when we remove packages that
shoud not be installed on ARM works. But if we are running actual
pytest tests on ARM, we do not need to run those tests any more.


^ 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 airflow-core/newsfragments.

@potiuk potiuk requested review from ashb and gopidesupavan as code owners May 5, 2025 11:22
@potiuk potiuk changed the title Run parallel tess for ARM platform Run parallel tests for ARM platform May 5, 2025
@potiuk potiuk force-pushed the add-arm-tests branch 5 times, most recently from 5f4d41f to 0fb76c6 Compare May 5, 2025 11:39
@potiuk potiuk force-pushed the add-arm-tests branch 3 times, most recently from f9d99d0 to 9ce9f07 Compare May 5, 2025 13:52
@potiuk potiuk requested a review from jedcunningham as a code owner May 5, 2025 13:52
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.

Super cool, now we have both :)

Copy link
Member

@jason810496 jason810496 left a comment

Choose a reason for hiding this comment

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

Rerun the test as it seems to be flaky.

Copy link
Contributor

@amoghrajesh amoghrajesh left a comment

Choose a reason for hiding this comment

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

👏🏽

@potiuk potiuk force-pushed the add-arm-tests branch 2 times, most recently from 726a785 to 221fc39 Compare May 6, 2025 08:03
@potiuk
Copy link
Member Author

potiuk commented May 6, 2025

For now I disabled the "pull request" trigger:

The tests will run:

  • canary runs on schedule (shifted by 3 hours from the regular AMD schedule)
  • when we merge to any of the v* branches
  • when we trigger it manually with workflow-dispatch

This will not have impact on regular PRs and we will have time to observe stability

Since we have `ubintu22.04-arm` public runners available, we should
be able to run a set of parallel tests for ARM - this would make our
ARM images move out of experimental phase.

We are not running "all" tests - only those that make sense to run
on ARM for "production" quality.

MySQL tests have some timeouts and run longer on ARM, that's why we
do not run MySQL tests on ARM as well.

We can also get rid of the "ARM collection" test that was introduced
to test if just **collection** of tests when we remove packages that
shoud not be installed on ARM works. But if we are running actual
pytest tests on ARM, we do not need to run those tests any more.
@potiuk potiuk merged commit 3198aad into apache:main May 6, 2025
95 checks passed
@potiuk potiuk deleted the add-arm-tests branch May 6, 2025 09:48
@potiuk potiuk added this to the Airflow 3.0.1 milestone May 6, 2025
potiuk added a commit to potiuk/airflow that referenced this pull request May 6, 2025
Since we have `ubintu22.04-arm` public runners available, we should
be able to run a set of parallel tests for ARM - this would make our
ARM images move out of experimental phase.

We are not running "all" tests - only those that make sense to run
on ARM for "production" quality.

MySQL tests have some timeouts and run longer on ARM, that's why we
do not run MySQL tests on ARM as well.

We can also get rid of the "ARM collection" test that was introduced
to test if just **collection** of tests when we remove packages that
shoud not be installed on ARM works. But if we are running actual
pytest tests on ARM, we do not need to run those tests any more.
(cherry picked from commit 3198aad)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk added a commit that referenced this pull request May 6, 2025
Since we have `ubintu22.04-arm` public runners available, we should
be able to run a set of parallel tests for ARM - this would make our
ARM images move out of experimental phase.

We are not running "all" tests - only those that make sense to run
on ARM for "production" quality.

MySQL tests have some timeouts and run longer on ARM, that's why we
do not run MySQL tests on ARM as well.

We can also get rid of the "ARM collection" test that was introduced
to test if just **collection** of tests when we remove packages that
shoud not be installed on ARM works. But if we are running actual
pytest tests on ARM, we do not need to run those tests any more.
(cherry picked from commit 3198aad)
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