Closed Bug 1565098 Opened 5 years ago Closed 5 years ago

Intermittent mozdevice.adb.ADBTimeoutError: args: adb wait-for-device shell getprop ro.product.cpu.abi; echo adb_returncode=$?, exitcode: None, stdout:

Categories

(Firefox for Android Graveyard :: Testing, defect, P5)

defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1500266

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: intermittent-failure, regression)

Filed by: csabou [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=255750155&repo=autoland
Full log: https://queue.taskcluster.net/v1/task/YxmbcurMRuGfJFlnNezNPg/runs/0/artifacts/public/logs/live_backing.log


2019-07-10 21:28:15,922 INFO Native pidof support: True
Traceback (most recent call last):
File "/builds/taskcluster/script.py", line 160, in <module>
sys.exit(main())
File "/builds/taskcluster/script.py", line 111, in main
device = ADBAndroid(device=env['DEVICE_SERIAL'])
File "/usr/local/lib/python2.7/dist-packages/mozdevice/adb.py", line 754, in init
abi = self.get_prop("ro.product.cpu.abi", timeout=timeout)
File "/usr/local/lib/python2.7/dist-packages/mozdevice/adb.py", line 1587, in get_prop
output = self.shell_output('getprop %s' % prop, timeout=timeout)
File "/usr/local/lib/python2.7/dist-packages/mozdevice/adb.py", line 1467, in shell_output
raise ADBTimeoutError("%s" % adb_process)
mozdevice.adb.ADBTimeoutError: args: adb wait-for-device shell getprop ro.product.cpu.abi; echo adb_returncode=$?, exitcode: None, stdout:
[taskcluster 2019-07-10T21:33:16.216Z] Exit Code: 1
[taskcluster 2019-07-10T21:33:16.216Z] User Time: 197.467ms
[taskcluster 2019-07-10T21:33:16.216Z] Kernel Time: 104.385ms
[taskcluster 2019-07-10T21:33:16.216Z] Wall Time: 5m5.411831147s
[taskcluster 2019-07-10T21:33:16.216Z] Result: FAILED
[taskcluster 2019-07-10T21:33:16.216Z] === Task Finished ===

Type: -- → defect
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.