-
-
Notifications
You must be signed in to change notification settings - Fork 30.8k
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
test_math.test_sumprod_stress() takes 5 minutes on debug build #110327
Comments
Timings as JUnit XML of |
test_math.test_sumprod_stress() alone takes 5 min 13 sec. The test was added by issue GH-100485: commit 47b9f83. |
This test uses 9 pools of lengths: [10, 9, 9, 11, 10, 9, 8, 5, 8]. It uses 4 nested loops for a total of 5,969,664 iterations. IMO that's excessive and it should be possible to minimize the test to a few cases. I don't think that there is a need to test 5,969,664 cases. |
@rhettinger @serhiy-storchaka: Can you please have a look at test_math.test_sumprod_stress() and see if we can test a few cases, rather than testing 5,969,664 cases? On my laptop with Python built with |
|
Sorry, I don't know exactly what it is testing and what can be cut out without losing the value of the test. |
@vstinner, |
Well, apparently, other people don't care much, so let's leave it like that for now. If someone wants to propose a change, please open a new issue. |
On the " PPC64LE Fedora Stable Clang 3.x" with Python build by "/configure CC=clang LD=clang --with-pydebug", test_math takes 7 min 39 sec:
Can we split test_math into a test package made of multiple tests to run them in parallel?
Should we remove/skip some slow tests? Buildbot uses
--slow-ci
which enables-u all
resources.The text was updated successfully, but these errors were encountered: