ImageImage

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: test_weakref super slow on RPi Zero
Type: Stage: resolved
Components: Tests Versions: Python 3.7
process
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: Nosy List: DNSGeek, iritkatriel, mcepl, vstinner
Priority: normal Keywords:

Created on 2019-03-19 17:17 by DNSGeek, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Messages (3)
msg338390 - (view) Author: Thomas Knox (DNSGeek) Date: 2019-03-19 17:17
When building Python 3.7.2 on a Raspberry Pi Zero W, it takes over 6 hours to run test_weakref, and almost 15 hours total to run through all the tests.

14:28:14 load avg: 1.00 [396/416] test_weakset -- test_weakref passed in 6 hour 24 min

Does it really need to take this long for one test?
msg351672 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2019-09-10 14:26
How long take other tests on Raspberry Pi Zero W?

You can try:

./python -m test -j0 --slowest

-j0 spawns one job per CPU. I don't know how many CPUs have this hardware.

--slowest gives the timing of the 10 slowest tests.

But even without --slowest, Python displays the test duration if a test takes longer than 30 seconds.
msg410661 - (view) Author: Irit Katriel (iritkatriel) * (Python committer) Date: 2022-01-15 20:00
3.7 is no longer maintained. Please create a new issue if you are seeing slow tests with a current version of python (ideally 3.10 or one of the 3.11 alphas), and you are interested in investigating along the lines of Victor's suggestion.
History
Date User Action Args
2022-04-11 14:59:12adminsetgithub: 80550
2022-01-15 20:00:58iritkatrielsetstatus: open -> closed

nosy: + iritkatriel
messages: + msg410661

resolution: out of date
stage: resolved
2019-09-10 14:26:55vstinnersetnosy: + vstinner
messages: + msg351672
2019-09-10 14:19:43mceplsetnosy: + mcepl
2019-03-19 17:17:17DNSGeekcreate