So why can't you just run "make test" if that's faster? On Sun, Jan 28, 2018 at 8:30 PM, Nick Coghlan <ncogh...@gmail.com> wrote:
> On my current system, "make test" runs in around 3 minutes, while > "./python -m test" runs in around 16 minutes. And that's with "make > test" actually running more tests (since it enables several of the > "-u" options). > > The difference is that "make test" passes "-j0" and hence not only > uses all the available cores in the machines, but will also run other > tests while some tests are sleeping. > > How would folks feel about making "-j 0" the default in the test > suite, and then adjusted the handling of "-j 1" to switch back to the > current default single process mode? > > My rationale for that is to improve the default edit-test cycle in > local development, while still providing a way to force single-process > execution for failure investigation purposes. > > Cheers, > Nick. > > -- > Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/ > guido%40python.org > -- --Guido van Rossum (python.org/~guido)
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
