-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
MAINT make ClassifierChain test more efficient #28705
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
MAINT make ClassifierChain test more efficient #28705
Conversation
For the sake of curiosity, I triggered the pypy CI to check whether that would fix the timeout problem before we get to merge #28704 to main. |
I doubt that this is a single issue but more a combination of multiple small issues. In particular there seems to be quite some variability in the slowest tests. In the last four logs where PyPy passed, none of them mentioned this particular test, see below. Wild-guess: the fact that a test is slow does not necessarily indicate an issue in this particular test but it could be that memory usage is high (for example caused by another test running in parallel because we are using xdist or even previous tests) and the OS starts to swap and everything become slow.
|
And the change in this PR broken the 32-bit linux tests:
not sure why though, as I would not have expected this test to be particularly sensitive to platform bitness... |
Let's wait for the CI to complete for the sake of curiosity but I don't plan to invest more time on this. We can close without merging once the CI has ended. |
Platform bitness is probably not the culprit but we do need to fix the random seed. |
I pushed a commit to fix the |
from #28705 (comment)
The exemples recently added in the docstrings of fetchers have the effect that we now fetch the lfw datasets in all CI jobs. EDIT: I opened a dedicated issue for that (#28707) since it impacts all CI jobs |
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.
For completeness, I suspect this does not significantly improve the situation for PyPy.
I set auto-merge and pushed a commit to trigger the CI since the PyPy build timed out. |
As suggested in #27662 (comment).