[issue25796] Running test_multiprocessing_spawn is slow (more than 8 minutes)

2017-06-27 Thread STINNER Victor
STINNER Victor added the comment: Sorry, I failed to take a decision nor find a concrete action to do on this issue, so I just closed it. -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker

[issue25796] Running test_multiprocessing_spawn is slow (more than 8 minutes)

2016-02-12 Thread Ned Deily
Changes by Ned Deily : -- nosy: +davin, sbt ___ Python tracker ___ ___ Python-bugs-list

[issue25796] Running test_multiprocessing_spawn is slow (more than 8 minutes)

2015-12-04 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: First, we have to mark longest tests with @support.requires_resource('cpu'). -- nosy: +serhiy.storchaka ___ Python tracker

[issue25796] Running test_multiprocessing_spawn is slow (more than 8 minutes)

2015-12-04 Thread STINNER Victor
Changes by STINNER Victor : -- components: +Tests type: -> performance ___ Python tracker ___

[issue25796] Running test_multiprocessing_spawn is slow (more than 8 minutes)

2015-12-04 Thread STINNER Victor
New submission from STINNER Victor: Hi, When I run the Python test suite with "./python -m test -j0 -rW", test_multiprocessing_spawn is almost the latest one to run. Example: --- (...) [399/401/1] test_lib2to3 (68 sec) -- running: test_zipfile (43 sec), test_multiprocessing_spawn (484 sec)