Skip to content

TST: Move Linux ARM64 job from cron to CI#17657

Merged
pllim merged 4 commits intoastropy:mainfrom
pllim:free-arm-2
Jan 23, 2025
Merged

TST: Move Linux ARM64 job from cron to CI#17657
pllim merged 4 commits intoastropy:mainfrom
pllim:free-arm-2

Conversation

@pllim
Copy link
Member

@pllim pllim commented Jan 23, 2025

Description

This pull request is to fix #17656

After merge

  • Add new job as "required" in branch protection.
  • By checking this box, the PR author has requested that maintainers do NOT use the "Squash and Merge" button. Maintainers should respect this when possible; however, the final decision is at the discretion of the maintainer that merges the PR.

@pllim pllim added this to the v7.1.0 milestone Jan 23, 2025
@github-actions
Copy link
Contributor

Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.

  • Do the proposed changes actually accomplish desired goals?
  • Do the proposed changes follow the Astropy coding guidelines?
  • Are tests added/updated as required? If so, do they follow the Astropy testing guidelines?
  • Are docs added/updated as required? If so, do they follow the Astropy documentation guidelines?
  • Is rebase and/or squash necessary? If so, please provide the author with appropriate instructions. Also see instructions for rebase and squash.
  • Did the CI pass? If no, are the failures related? If you need to run daily and weekly cron jobs as part of the PR, please apply the "Extra CI" label. Codestyle issues can be fixed by the bot.
  • Is a change log needed? If yes, did the change log check pass? If no, add the "no-changelog-entry-needed" label. If this is a manual backport, use the "skip-changelog-checks" label unless special changelog handling is necessary.
  • Is this a big PR that makes a "What's new?" entry worthwhile and if so, is (1) a "what's new" entry included in this PR and (2) the "whatsnew-needed" label applied?
  • At the time of adding the milestone, if the milestone set requires a backport to release branch(es), apply the appropriate "backport-X.Y.x" label(s) before merge.

@github-actions
Copy link
Contributor

👋 Thank you for your draft pull request! Do you know that you can use [ci skip] or [skip ci] in your commit messages to skip running continuous integration tests until you are ready?

@pllim pllim marked this pull request as ready for review January 23, 2025 02:57
@pllim pllim requested review from a team and Cadair January 23, 2025 02:57
Copy link
Member

@bsipocz bsipocz left a comment

Choose a reason for hiding this comment

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

Looks good, one minor comment to consider.

targets: |
- cp311-manylinux_x86_64

test_arm64:
Copy link
Member

Choose a reason for hiding this comment

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

now that this runs in the main matrix, you may want to consider removing one of the other linux jobs?

Copy link
Member Author

Choose a reason for hiding this comment

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

Any suggestion? It still needs to be a separate job due to different env var, I think.

All the existing Linux jobs seem to be specialized (all deps, cov, run twice, etc). And I am not sure which one is most suited to use this new runner.

Copy link
Member

Choose a reason for hiding this comment

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

It still needs to be a separate job due to different env var, I think.

It shouldn't you can set per-job env vars: https://github-actions-workflows.openastronomy.org/en/latest/tox.html#setenv

Copy link
Contributor

Choose a reason for hiding this comment

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

Why not let the arm job do the run-twice or so? That would seem unlikely to be architecture dependent.

Copy link
Member Author

Choose a reason for hiding this comment

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

I have to check the runner specs again. I think we have to reduce -n=4 to -n=2 if we switch. Is that a problem?

Copy link
Member Author

Choose a reason for hiding this comment

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

@bsipocz
Copy link
Member

bsipocz commented Jan 23, 2025

Also, maybe backport or have this add to the CI on the bugfix branch, too.

@pllim

This comment was marked as resolved.

@pllim
Copy link
Member Author

pllim commented Jan 23, 2025

Huh... I applied the suggestions and the job failed pretty fast but error is cryptic to me. Not sure if it is related to the yellow GitHub status or not.

@@ -93,6 +93,10 @@ jobs:

- name: Python 3.11 Double test (Run tests twice)
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
- name: Python 3.11 Double test (Run tests twice)
- name: Python 3.11 Double test (Run tests twice) [aarch64]

Copy link
Member Author

Choose a reason for hiding this comment

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

But then I have to go update the branch protection and all the PRs will need rebasing. 😬

Copy link
Member Author

Choose a reason for hiding this comment

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

@bsipocz and @mhvk , any preference about keeping or changing job name?

Copy link
Contributor

Choose a reason for hiding this comment

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

Happy to leave as is to avoid giving people pain, but even happier to leave the decision up to you!

Copy link
Member

Choose a reason for hiding this comment

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

Honestly, I would put this as the first word as the most important attribute of the job (as the end will be chopped down anyway), but also it doesn't matter much if too much pain.

Copy link
Member Author

Choose a reason for hiding this comment

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

Maybe we can do it when we bump Python version in the future since the name would change anyway...

@Cadair
Copy link
Member

Cadair commented Jan 23, 2025

yeah it looks like it failed on git checkout so I would say that's a service issue.

@pllim pllim modified the milestone: v7.0.1 Jan 23, 2025
@pllim pllim merged commit 7ef2800 into astropy:main Jan 23, 2025
0 of 2 checks passed
@lumberbot-app

This comment was marked as resolved.

@pllim
Copy link
Member Author

pllim commented Jan 23, 2025

Thanks, all!

@pllim pllim deleted the free-arm-2 branch January 23, 2025 21:37
pllim added a commit to pllim/astropy that referenced this pull request Jan 23, 2025
pllim added a commit that referenced this pull request Jan 23, 2025
Backport PR #17657: TST: Move Linux ARM64 job from cron to CI
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.

TST: Move Linux ARM64 job from weekly cron to main CI

4 participants