Closed
Bug 1582328
Opened 5 years ago
Closed 5 years ago
Get better error messages when a mozmill test file has a problem
Categories
(Thunderbird :: Testing Infrastructure, enhancement)
Thunderbird
Testing Infrastructure
Tracking
(Not tracked)
RESOLVED
FIXED
Thunderbird 71.0
People
(Reporter: darktrojan, Assigned: darktrojan)
Details
Attachments
(1 file, 1 obsolete file)
1.86 KB,
patch
|
mkmelin
:
review+
|
Details | Diff | Splinter Review |
At the moment, if a test file throws an exception when loaded (for example it tries to import from a URL that doesn't exist and throws NS_ERROR_FILE_NOT_FOUND), the log shows no error message and not even the file name.
This can be improved by sending better information to the log writer. I can't actually get just the exception message itself (the exception object is weird), so I'll send the whole string representation.
Result:
SUMMARY-UNEXPECTED-FAIL | testCategoryColors.js | testCategoryColors.js::<TOP_LEVEL>
EXCEPTION: [Exception... "File error: Not found" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: file:///home/geoff/mozilla/mozilla-central/obj-artifact/_tests/mozmill/stage/preferences/testCategoryColors.js :: <TOP_LEVEL> :: line 9" data: no]
at: testCategoryColors.js line 9
Assignee | ||
Comment 1•5 years ago
|
||
Attachment #9093765 -
Flags: review?(mkmelin+mozilla)
Assignee | ||
Comment 2•5 years ago
|
||
Great, even the core code can't decide if it's filename or fileName. :-/
Attachment #9093765 -
Attachment is obsolete: true
Attachment #9093765 -
Flags: review?(mkmelin+mozilla)
Attachment #9093802 -
Flags: review?(mkmelin+mozilla)
Updated•5 years ago
|
Attachment #9093802 -
Flags: review?(mkmelin+mozilla) → review+
Pushed by geoff@darktrojan.net:
https://hg.mozilla.org/comm-central/rev/14db01bcabd2
Get better error messages when a mozmill test file has a problem; r=mkmelin DONTBUILD
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•5 years ago
|
Target Milestone: --- → Thunderbird 71.0
You need to log in
before you can comment on or make changes to this bug.
Description
•