regrtest takes between 10 and 20 minutes to run the full test suite. It would be nice to see the progress of the test suite with a kind of progress bar. Add the test number would be enough: $ ./python Lib/test/regrtest.py ... test_grammar (1/340) test_opcodes (2/340) test_dict (3/340) test_builtin (4/340) test_exceptions (5/340) test_types (6/340) test_unittest (7/340) ... Attached patch implements that (classic version and multiprocess version).
> I personally am fine with judging the progress by the filenames The new displayed test names only inform you that regrtest is not blocked, but you don't know how many tests remain if: - you use -j option (which shuffle the list at little bit) - you use -r (random): I think that the buildbots use them. If a buildbot hang, it's not easy to see how many tests were executed (and how many remain) - you specify a list of test names on the command line
Higher/lower bounds for me: - Quad core @ 2.5 GHz with -j4: 2 min 40 sec - Pentium4 @ 3 GHz (hyperthreading) without -j: 11 min 21 sec Sometimes I forget to use -j, and sometimes I cannot use it (eg. see my last patches to support --without-threads ;-)). When it takes more than 30 seconds, I would like a progress bar to estimate (myself) the remaing time :-)
Hmm, I see only one objection... and I think readability will be much less affected if the format is [ 1/340] test_grammar [ 2/340] test_opcodes [ 3/340] test_dict or somesuch.
