-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
CI: run tests with pypy3 on circleci #8783
Conversation
6973f95
to
e73785e
Compare
891165a
to
72f3e12
Compare
4f77aa4
to
a018c1b
Compare
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.
All tests in the CI matrix are passing, including the full pypy3 test suite added in here. The new pypy CI job takes about 26 minutes, which seems ok.
+1 to merge; since it is a change to our CI I'll leave it open for a bit longer.
Just curious what is the reason to use CircleCI instead of Travis here? Because there is a CircleCI pypy image? To keep Travis times from increasing further? 26 minutes seems fine. +1 for merge from me |
The reason is that I initially expected it to be too close to Travis
time limits, and I happened to have an example circleci pypy config at
hand from which to copypaste. However, using "standard" docker image
(https://hub.docker.com/r/library/pypy/) indeed is probably easier on
circleci, and it's probably faster like this since it runs in parallel
with travis.
|
I'll make a note to merge on Friday if there are no objections to the CI expansion here by then. |
Having all tests pass on pypy is great! |
Ok, looks like solid core dev support and no objections so in it goes. |
* MAINT: make parallelism in tools/cythonize.py adjustable * CI: run tests with pypy3 on circleci (cherry picked from commit bdfce64)
Supporting also pypy3 as a platform probably does not take much extra effort (all tests pass for newest pypy release, with numpy master), and we can add it to CI to keep it working.