-
Notifications
You must be signed in to change notification settings - Fork 61
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
Set Python to known version for all CI workflows #2058
Conversation
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.
This is ok for me, but you add two workflow runs. CI is still taking time and costing someone. Do we really need that bit extra?
This is a draft PR needed for triggering the workflows, and I'm still investigating the cause of the problem. An important clue is the fact that Update:
|
Update: Github have a bit of GCC 12 missing in their image, thanks @schmitts: actions/runner-images#6724 Meanwhile we can stick to 20.04 for Spack workflows. |
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.
LGTM
* Python Wheel workflow uses `ubuntu-20.04` to fix the build * In #2058 I forgot to update `ciwheel.yml` * Why this is necessarily: still have not figured it out. `cibuildwheel` builds and tests in it's own container... * [x] https://github.com/brenthuisman/arbor/actions/runs/3704419712 * Small change to make `musllinux` wheels build. They don't pass testing yet, so I don't add them to the workflow but that can be solved/added [later](pypa/cibuildwheel#1376) * The reason for using `ubuntu-20.04` in the Spack workflow should [no longer exist](actions/runner-images#6724).
See the same jobs fail, which turn out to execute using different Python versions: