Closed Bug 967318 Opened 11 years ago Closed 11 years ago

ScriptTimeoutExceptions should be reported with the failure on the same line as the test name

Categories

(Remote Protocol :: Marionette, defect, P1)

defect

Tracking

(firefox30 wontfix, firefox31 wontfix, firefox32 fixed, b2g-v1.3 fixed, b2g-v1.3T fixed, b2g-v1.4 fixed, b2g-v2.0 fixed)

RESOLVED FIXED
mozilla32
Tracking Status
firefox30 --- wontfix
firefox31 --- wontfix
firefox32 --- fixed
b2g-v1.3 --- fixed
b2g-v1.3T --- fixed
b2g-v1.4 --- fixed
b2g-v2.0 --- fixed

People

(Reporter: jgriffin, Assigned: automatedtester)

References

(Blocks 1 open bug)

Details

(Keywords: pi-marionette-runner, sheriffing-P1, Whiteboard: [runner])

Attachments

(1 file)

Marionette tests are currently reporting ScriptTimeoutExceptions in a way that makes them difficult to sheriff correctly. They're reported like: 07:45:13 ERROR - raise ScriptTimeoutException(message=message, status=status, stacktrace=stacktrace) 07:45:13 ERROR - ScriptTimeoutException: ScriptTimeoutException: timed out 07:45:13 INFO - TEST-UNEXPECTED-FAIL | test_outgoing_emergency_in_airplane_mode.js | 07:45:13 INFO - ---------------------------------------------------------------------- (see https://tbpl.mozilla.org/php/getParsedLog.php?id=34012307&tree=Fx-Team#error2) ...but we'd like them to be reported like: 07:45:13 ERROR - raise ScriptTimeoutException(message=message, status=status, stacktrace=stacktrace) 07:45:13 ERROR - TEST-UNEXPECTED-FAIL | test_outgoing_emergency_in_airplane_mode.js | ScriptTimeoutException: ScriptTimeoutException: timed out 07:45:13 INFO - ---------------------------------------------------------------------- I.e., "ScriptTimeoutException" should be given as the reason for the failure in the TEST-UNEXPECTED-FAIL line. We used to handle this better, see e.g., bug 837827.
This would make life much easier for TBPL starring.
Keywords: sheriffing-P1
I'm distracted by another task right now, but for the record I think it would be useful to introduce a test case that ensured tbpl-friendly exception formatting so that this doesn't get repeated.
Whiteboard: [runner]
Blocks: log-SnR
Priority: -- → P1
Assignee: nobody → dburns
Blocks: 948895
pushed to try https://tbpl.mozilla.org/?tree=Try&rev=3be9ddc32a9d Lets see if the results are better with intermittents
Flags: needinfo?(dburns)
Comment on attachment 8416554 [details] [diff] [review] Put the error reason in the message that is reported on TBPL for easier starring \o/
Attachment #8416554 - Flags: review+
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla32
Depends on: 1006511
Flags: needinfo?(ryanvm)
Blocks: 1017559
Blocks: 1020296
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: