Closed
Bug 809977
Opened 13 years ago
Closed 13 years ago
Allow output with progress bar
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla20
People
(Reporter: sfink, Assigned: sfink)
Details
Attachments
(1 file)
5.35 KB,
patch
|
terrence
:
review+
sfink
:
checkin+
|
Details | Diff | Splinter Review |
The progress bar goes away if you ask for any output. I really miss the progress bar when it isn't here.
Assignee | ||
Comment 1•13 years ago
|
||
I am anal. The extra blank line was annoying me.
Attachment #679767 -
Flags: review?(terrence)
Comment 2•13 years ago
|
||
Comment on attachment 679767 [details] [diff] [review]
Allow output with progress bar
Review of attachment 679767 [details] [diff] [review]:
-----------------------------------------------------------------
::: js/src/tests/lib/progressbar.py
@@ +21,5 @@
> assert not self.conservative_isatty()
> assert limit < 9999
>
> self.prior = None
> + self.atbol = True
|atbol| left me scratching my head for a good few seconds. Can we change this to "atLineStart" or something equivalent?
::: js/src/tests/lib/results.py
@@ +120,5 @@
> show = self.options.show
> if self.options.failed_only and dev_label not in ('REGRESSIONS', 'TIMEOUTS'):
> show = False
> + if show:
> + self.pb.beginline()
Now that we have a generic |if show| path, can we nest the next three |if show and something| commands beneath this and remove |show and| from the nested branches?
Attachment #679767 -
Flags: review?(terrence) → review+
Assignee | ||
Updated•13 years ago
|
Attachment #679767 -
Flags: checkin+
Assignee | ||
Comment 3•13 years ago
|
||
![]() |
||
Comment 4•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla20
You need to log in
before you can comment on or make changes to this bug.
Description
•