-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
CI Migrates pypy3 test to Azure #21005
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
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.
Thanks @thomasjpfan LGTM
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.
Thank you @thomasjpfan!
Just a question, when is the pypy3
job supposed to be run?
It used to be a nightly build, now it runs in all push events (PR or main branch). It takes 33min to run so it's longer than the other builds but there is another windows build that takes 30 min already. Maybe this is fine. If it proves to slow, we can always update the config to run it in a schedule task + a manual commit msg trigger in PRs. |
Reference Issues/PRs
Fixes #20995
What does this implement/fix? Explain your changes.
This PR:
posix-32.yml
to run on any docker container with some adjustments for mamba and pypy.Any other comments?
Note this PR disables pandas, because I ran into this strange error with pandas installed. We can look into the error in a follow up PR.