Closed
Bug 476185
Opened 15 years ago
Closed 15 years ago
runtests.py should print out firefox-bin's stdout immediately
Categories
(Testing :: Mochitest, defect)
Testing
Mochitest
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.9.2a1
People
(Reporter: smaug, Assigned: bjarne)
References
Details
(Keywords: fixed1.9.1, Whiteboard: [fixed1.9.1b4])
Attachments
(1 file, 1 obsolete file)
1003 bytes,
patch
|
Waldo
:
review+
|
Details | Diff | Splinter Review |
Comment 1•15 years ago
|
||
I see this bug too, on my local Windows 2000.
Reporter | ||
Updated•15 years ago
|
Severity: normal → major
Assignee | ||
Updated•15 years ago
|
Assignee: nobody → bjarne
Assignee | ||
Comment 2•15 years ago
|
||
The iterator over file-objects has it's own buffering. This patch replaces it with a more primitive loop. On my Ubuntu-system this works nicely with no extra options to python. On other systems, the -u option may have to be used to avoid stdio-buffering.
Attachment #362086 -
Flags: review?(jwalden+bmo)
Comment 3•15 years ago
|
||
Comment on attachment 362086 [details] [diff] [review] Quick fix to avoid in-built buffering in iterators >+ while (line != ""): Ax the unnecessary parentheses, upload a patch, and I'll push. Gah, I didn't realize that happened...
Attachment #362086 -
Flags: review?(jwalden+bmo) → review+
Assignee | ||
Comment 4•15 years ago
|
||
Attachment #362086 -
Attachment is obsolete: true
Attachment #362092 -
Flags: review?(jwalden+bmo)
cool!
Comment 6•15 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/87b0a5610a8d
Status: NEW → RESOLVED
Closed: 15 years ago
Flags: in-testsuite-
Hardware: x86 → All
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9.2a1
Comment 7•15 years ago
|
||
Comment on attachment 362092 [details] [diff] [review] Removed parentheses... [Checkin: See comment 6 & 13] For future reference, if a patch receives a + but also has comments to be addressed on it, you can just upload a new version of the patch with the comments addressed and don't have to worry about getting another review of it -- it's a measure of trust/confidence that the changes can be made without a precise lookthrough again to be sure they were made correctly.
Attachment #362092 -
Flags: review?(jwalden+bmo) → review+
Comment 8•15 years ago
|
||
I don't see ANY output on Mac.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 9•15 years ago
|
||
(In reply to comment #8) > I don't see ANY output on Mac. To be explicit, which check-in caused this ? Comment 6 ? And which behavior did you get before ?
Assignee | ||
Comment 10•15 years ago
|
||
(In reply to comment #8) > I don't see ANY output on Mac. I dont't have access to a Mac at the moment... Is there no output whatsoever? What if you disable this particular patch and keep the one for bug #464191? Did you try running python with the -u option? Btw, didn't this one land some time ago (ref comment #3 and comment #6)? Did anyone else see this problem?
Comment 11•15 years ago
|
||
Guys, my apologies. Debug build works as expected but I was running an optimized build that has no output, I was convinced it had some output in the past but probably never had. Sorry for this spam!
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → FIXED
Updated•15 years ago
|
Whiteboard: [needs 1.9.1 landing: after bug 464191]
Assignee | ||
Comment 12•15 years ago
|
||
Phew... I was starting to get worried... :) Thanks for clearing it up.
Comment 13•15 years ago
|
||
Comment on attachment 362092 [details] [diff] [review] Removed parentheses... [Checkin: See comment 6 & 13] http://hg.mozilla.org/releases/mozilla-1.9.1/rev/10fb2d2f8535 After fixing context for: { patching file build/automation.py.in Hunk #1 FAILED at 441 1 out of 1 hunks FAILED }
Attachment #362092 -
Attachment description: Removed parentheses... → Removed parentheses...
[Checkin: See comment 6 & 13]
Comment 14•15 years ago
|
||
V.Fixed, locally.
Status: RESOLVED → VERIFIED
Keywords: regression → fixed1.9.1
Whiteboard: [needs 1.9.1 landing: after bug 464191] → [fixed1.9.1b4]
You need to log in
before you can comment on or make changes to this bug.
Description
•