TST: Move Linux ARM64 job from cron to CI#17657
Conversation
|
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.
|
|
👋 Thank you for your draft pull request! Do you know that you can use |
bsipocz
left a comment
There was a problem hiding this comment.
Looks good, one minor comment to consider.
.github/workflows/ci_workflows.yml
Outdated
| targets: | | ||
| - cp311-manylinux_x86_64 | ||
|
|
||
| test_arm64: |
There was a problem hiding this comment.
now that this runs in the main matrix, you may want to consider removing one of the other linux jobs?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
There was a problem hiding this comment.
Why not let the arm job do the run-twice or so? That would seem unlikely to be architecture dependent.
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
Oh nvm... maybe we get 4 still. I must be confused with the paid one. https://docs.github.com/en/actions/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners#standard-github-hosted-runners-for-public-repositories
|
Also, maybe backport or have this add to the CI on the bugfix branch, too. |
This comment was marked as resolved.
This comment was marked as resolved.
|
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) | |||
There was a problem hiding this comment.
| - name: Python 3.11 Double test (Run tests twice) | |
| - name: Python 3.11 Double test (Run tests twice) [aarch64] |
There was a problem hiding this comment.
But then I have to go update the branch protection and all the PRs will need rebasing. 😬
There was a problem hiding this comment.
Happy to leave as is to avoid giving people pain, but even happier to leave the decision up to you!
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Maybe we can do it when we bump Python version in the future since the name would change anyway...
|
yeah it looks like it failed on git checkout so I would say that's a service issue. |
This comment was marked as resolved.
This comment was marked as resolved.
|
Thanks, all! |
Backport PR #17657: TST: Move Linux ARM64 job from cron to CI
Description
This pull request is to fix #17656
After merge
Add new job as "required" in branch protection.