Re: [Python-Dev] Extremely slow test modules

03.06.17 16:01, Antoine Pitrou пише: On Sat, 3 Jun 2017 15:28:18 +0300 Serhiy Storchaka wrote: test_tools (in particular the test for the unparse.py script), test_tokenize, and test_lib2to3 read and proceed every Python file in the stdlib. This is necessary in full test

Re: [Python-Dev] Extremely slow test modules

On Sat, 3 Jun 2017 15:01:07 +0200 Antoine Pitrou wrote: > > > This is controlled by the cpy resource. > > I suggested to disable it on the slowest buildbots (-uall,-cpu). In that > > case tests are ran only for few random files. > > I don't really care about the

Re: [Python-Dev] Extremely slow test modules

On Sat, 3 Jun 2017 15:28:18 +0300 Serhiy Storchaka wrote: > > test_tools (in particular the test for the unparse.py script), > test_tokenize, and test_lib2to3 read and proceed every Python file in > the stdlib. This is necessary in full test run because some syntax >

Re: [Python-Dev] Extremely slow test modules

03.06.17 13:31, Antoine Pitrou пише: Is there a reason some of our tests are excruciatingly slow in `-uall` mode? `test_multiprocessing_spawn` is understandable (after all, it will spawn a new executable for each subprocess), but other tests leave me baffled: - test_tools: 7 min 41 sec -

[Python-Dev] Extremely slow test modules

Hi, Is there a reason some of our tests are excruciatingly slow in `-uall` mode? `test_multiprocessing_spawn` is understandable (after all, it will spawn a new executable for each subprocess), but other tests leave me baffled: - test_tools: 7 min 41 sec - test_tokenize: 6 min 23 sec -