Closed
Bug 479660
Opened 15 years ago
Closed 15 years ago
Tinderbox "Build Error Summary" does not include crashtest crash
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jruderman, Assigned: bhearsum)
Details
Attachments
(1 file, 1 obsolete file)
1.19 KB,
patch
|
ted
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1235268007.1235274191.14714.gz&fulltext=1 TinderboxPrint shows the crashtest fail, but the "summary" does not, so I have to load the full log and search for "TinderboxPrint" to find out which test the crash was after :( This might be a dup of bug 457976.
Updated•15 years ago
|
Assignee: build → nobody
Component: Tinderbox Configuration → Release Engineering
QA Contact: ccooper → release
Comment 1•15 years ago
|
||
This could be a releng bug (to change/add the output there), or a Webtools:Tinderbox bug (to change ep_unittest.pl to pick this up for the summary).
Assignee | ||
Comment 2•15 years ago
|
||
I've got a couple of ideas here.
Assignee: nobody → bhearsum
Priority: -- → P2
Assignee | ||
Comment 3•15 years ago
|
||
I went with 'Unknown Error:' here because it seems that 'Error:' won't be picked up by ep_unittest.pl (/\WError: /i). Anyways, this should catch all crashes in any of the unittest steps and give them a more useful Brief Log.
Attachment #363690 -
Flags: review?
Assignee | ||
Updated•15 years ago
|
Attachment #363690 -
Flags: review? → review?(ted.mielczarek)
Assignee | ||
Updated•15 years ago
|
Status: NEW → ASSIGNED
Comment 4•15 years ago
|
||
Comment on attachment 363690 [details] [diff] [review] always print an error message for unittest steps that return non-zero + if "program finished with exit code" in line: Is this necessary given the return code check?
Attachment #363690 -
Flags: review?(ted.mielczarek) → review+
Assignee | ||
Comment 5•15 years ago
|
||
(In reply to comment #4) > (From update of attachment 363690 [details] [diff] [review]) > + if "program finished with exit code" in line: > > Is this necessary given the return code check? Good point. I should be able to just check the return code outside the loop and construct the line manually.
Assignee | ||
Comment 6•15 years ago
|
||
Attachment #363945 -
Flags: review?(ted.mielczarek)
Assignee | ||
Updated•15 years ago
|
Attachment #363690 -
Attachment is obsolete: true
Updated•15 years ago
|
Attachment #363945 -
Flags: review?(ted.mielczarek) → review+
Assignee | ||
Comment 7•15 years ago
|
||
Comment on attachment 363945 [details] [diff] [review] check the exit code outside of the loop changeset: 205:f85737806a5c
Attachment #363945 -
Flags: checked‑in+ checked‑in+
Assignee | ||
Comment 8•15 years ago
|
||
master reconfig'ed for this.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment 9•15 years ago
|
||
(In reply to comment #7) > (From update of attachment 363945 [details] [diff] [review]) > changeset: 205:f85737806a5c Ftr, http://hg.mozilla.org/build/buildbotcustom/rev/f85737806a5c itself is empty: somehow, this patch content got merged into the previous check-in: http://hg.mozilla.org/build/buildbotcustom/rev/c2484f6c012e
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•