A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2017-June/148218.html below:

[Python-Dev] Extremely slow test modules

[Python-Dev] Extremely slow test modules [Python-Dev] Extremely slow test modulesAntoine Pitrou solipsis at pitrou.net
Sat Jun 3 06:31:55 EDT 2017
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
- test_datetime: 6 min 3 sec
- test_lib2to3: 5 min 25 sec
[excerpt from recent Travis CI logs]

Why does datetime, 2to3 or tokenize testing take so long?  And do we
have so many tools that it should take 7 minutes to run all of them?
I must admit, I don't understand how we got to such a point.

Regards

Antoine.


More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4