New submission from Brett Cannon: If we guaranteed that the slowest tests in the test suite started early enough in the test run to complete before the final test finished, we could shave off several minutes worth of time in cases where the slowest tests are the hold-up. So perhaps if we randomly inserted the 10 slowest tests in the first 3/4 of the complete test list we could make sure they finish early enough?
---------- components: Tests messages: 294658 nosy: brett.cannon priority: normal severity: normal status: open title: Run Python's slowest tests in the first 3/4 of tests when using -r versions: Python 3.7 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30498> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
