[issue8560] regrtest: add a minimal "progress bar"

Georg Brandl added the comment: Committed patch adding the [x/y] style indicator in r83543. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

[issue8560] regrtest: add a minimal "progress bar"

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue8560] regrtest: add a minimal "progress bar"

Antoine Pitrou added the comment: Georg's suggestion is rather nice. -- nosy: +pitrou versions: +Python 3.1 ___ Python tracker ___ ___

[issue8560] regrtest: add a minimal "progress bar"

Georg Brandl added the comment: 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. -- nosy: +georg.brandl resolution: invalid -> status: closed -> open

[issue8560] regrtest: add a minimal "progress bar"

STINNER Victor added the comment: Most developer are opposed to this feature, so I close this issue. -- resolution: -> invalid status: open -> closed ___ Python tracker ___

[issue8560] regrtest: add a minimal "progress bar"

STINNER Victor added the comment: 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 ;-)). Wh

[issue8560] regrtest: add a minimal "progress bar"

STINNER Victor added the comment: > 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

[issue8560] regrtest: add a minimal "progress bar"

R. David Murray added the comment: -1 IMO it just makes the output messier and less readable, and I personally am fine with judging the progress by the filenames. -- nosy: +r.david.murray ___ Python tracker _

[issue8560] regrtest: add a minimal "progress bar"

New submission from STINNER Victor : 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 ... te