Closed
Bug 1561737
Opened 6 years ago
Closed 6 years ago
Android gtest may not report ADBErrors correctly
Categories
(Testing :: GTest, defect)
Tracking
(firefox69 fixed)
RESOLVED
FIXED
mozilla69
| Tracking | Status | |
|---|---|---|
| firefox69 | --- | fixed |
People
(Reporter: gbrown, Assigned: gbrown)
References
Details
Attachments
(1 file)
https://treeherder.mozilla.org/logviewer.html#?job_id=253542109&repo=try
[task 2019-06-26T18:31:47.662Z] 18:31:47 INFO - gtest ERROR | ADBDevice.init: ls could not be found
Since no "ADBError"/"ADBTimeoutError" was logged, the task did not auto-retry.
|
Assignee | |
Comment 1•6 years ago
|
||
Including the traceback info will include the exception name, like "ADBError" which
should trigger the android-em task retry; it also provides more debugging info.
Pushed by gbrown@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5616b96450dc
Log full exception traceback from android gtest; r=bc
|
||
Comment 3•6 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox69:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
You need to log in
before you can comment on or make changes to this bug.
Description
•