-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
Rebuild for python310 (redux) #175
Conversation
…nda-forge-pinning 2021.11.09.00.35.45
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
PPC looks like it's going to be an utter mess of failures again (presumably the same kind of QEMU bugs that are responsible for the scipy test suite failing on PPC-via-QEMU; scipy is currently built without running the test suite, as people were opposed to dropping it completely, and preferred untested binaries to nothing, see discussion in conda-forge/scipy-feedstock#191). An excerpt:
|
So |
I'd be okay with untested binary for ppc |
+1 on my side for this release build |
Involuntarily. Both Travis and Drone became more or less unusable over the last 1-2 months. |
The following is hardly a picture of confidence (~1450 failures+errors), but I'm happy to go along with the more pragmatic approach here.
|
@isuruf @jakirkham |
there hasn't yet been a pypy run completed in QEMU on azure, so we take test timings of a cpython run that hit a slower agent (all added tests ran >80 sec there)
@conda-forge/scikit-learn |
yeah those are quite slow. Thanks for skipping them. |
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.
I think this makes sense.
Co-authored-by: Isuru Fernando <[email protected]>
win + pypy "only" ran into If desired, I can try something like setting the pagefile size explicitly (c.f. e.g. conda-forge/scipy-feedstock@fcf4f63) - not sure if that'll help though, as the error is usually more explicitly about running out of pagefile. |
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe:
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Someone feel like pressing the merge button? 🙃 |
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.
Minor comment otherwise LGTM. Thanks for working on this @h-vetinari !
- export OMP_NUM_THREADS=1 # [aarch64 or ppc64le] | ||
- pytest --pyargs sklearn -k "not ({{ tests_to_skip }})" -n {{ cpus }} --durations=50 {{ extra_pytest_args }} | ||
- pytest --pyargs sklearn -k "not ({{ tests_to_skip }})" -nauto --timeout=1200 --durations=50 # [not ppc64le] |
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.
The nauto is only reliable when psutils is installed. e.g. when running inside docker with limited CPU resources https://github.com/pytest-dev/pytest-xdist/blob/2bac85562b996059b152b3491d73ddbbc413318a/src/xdist/plugin.py#L30 is this the case in the CI? Otherwise it would often return say 16 CPU while CI can only use 2.
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.
Hm, interesting point. On azure this seems to work reliably, i.e. there are only ever 2-3 workers per image/run. It's IMO an improvement over explicitly setting a number of processors (as previously), which might then not all be available. Though even in that case, the CI passed, just slower due to contention.
Last commit is just a comment update; I believe this PR is ready for an automerge-label 🙃 |
It's done. Thanks again for your work @h-vetinari ! |
Hi! This is the friendly conda-forge automerge bot! I considered the following status checks when analyzing this PR:
Thus the PR was passing and merged! Have a great day! |
The win+pypy failure is spurious:
Can someone please press merge? I can also join as a maintainer if people want - that way I wouldn't have to ping as often 😋 |
Based on #174, but cleaning up the left over test skips, invocation & CPU settings from drone/travis.
Closes #174