Closed Bug 1538532 Opened 5 years ago Closed 5 years ago

Intermittent Uncaught exception: Traceback (most recent call last): after Finished verify-device step (failed)

Categories

(Testing Graveyard :: Autophone, defect, P5)

defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1504757

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: intermittent-failure, regression)

#[markdown(off)]
Filed by: ccoroiu [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=235705270&repo=autoland

https://queue.taskcluster.net/v1/task/MB7M7w0BSNmDOPKaDEZrcw/runs/0/artifacts/public/logs/live_backing.log

06:01:21 INFO - Running post-action listener: _resource_record_post_action
06:01:21 INFO - Running post-action listener: _start_resource_monitoring
06:01:21 INFO - Starting resource monitoring.
06:01:21 INFO - [mozharness: 2019-03-24 06:01:21.830045Z] Finished create-virtualenv step (success)
06:01:21 INFO - [mozharness: 2019-03-24 06:01:21.830373Z] Running verify-device step.
06:01:21 INFO - Running pre-action listener: _resource_record_pre_action
06:01:21 INFO - Running main action method: verify_device
06:01:21 INFO - mkdir: /builds/worker/workspace/build/blobber_upload_dir
06:01:21 INFO - Using adb 1.0.40
06:01:22 INFO - adbd not restarted as root
06:01:22 INFO - su -c supported
06:01:23 INFO - Running post-action listener: _resource_record_post_action
06:01:23 INFO - [mozharness: 2019-03-24 06:01:23.051694Z] Finished verify-device step (failed)
06:01:23 FATAL - Uncaught exception: Traceback (most recent call last):
06:01:23 FATAL - File "/builds/worker/workspace/mozharness/mozharness/base/script.py", line 2089, in run
06:01:23 FATAL - self.run_action(action)
06:01:23 FATAL - File "/builds/worker/workspace/mozharness/mozharness/base/script.py", line 2028, in run_action
06:01:23 FATAL - self._possibly_run_method(method_name, error_if_missing=True)
06:01:23 FATAL - File "/builds/worker/workspace/mozharness/mozharness/base/script.py", line 1983, in _possibly_run_method
06:01:23 FATAL - return getattr(self, method_name)()
06:01:23 FATAL - File "/builds/worker/workspace/mozharness/mozharness/mozilla/testing/android.py", line 566, in verify_device
06:01:23 FATAL - self.dump_perf_info()
06:01:23 FATAL - File "/builds/worker/workspace/mozharness/mozharness/mozilla/testing/android.py", line 259, in dump_perf_info
06:01:23 FATAL - out = self.shell_output(cmd)
06:01:23 FATAL - File "/builds/worker/workspace/mozharness/mozharness/mozilla/testing/android.py", line 344, in shell_output
06:01:23 FATAL - return self.device.shell_output(cmd, timeout=30)
06:01:23 FATAL - File "/builds/worker/workspace/mozharness/mozharness/mozilla/testing/android.py", line 65, in device
06:01:23 FATAL - verbose=True)
06:01:23 FATAL - File "/builds/worker/workspace/build/venv/lib/python2.7/site-packages/mozdevice/adb.py", line 664, in __init__
06:01:23 FATAL - raise ADBError("ADBDevice.__init__: ls could not be found")
06:01:23 FATAL - ADBError: ADBDevice.__init__: ls could not be found
06:01:23 FATAL - Running post_fatal callback...
06:01:23 FATAL - Exiting -1
06:01:23 INFO - Running post-run listener: _resource_record_post_run
06:01:23 INFO - Total resource usage - Wall time: 1s; CPU: 5.0%; Read bytes: 4128768; Write bytes: 0; Read time: 0; Write time: 0
06:01:23 INFO - TinderboxPrint: CPU usage<br/>5.5%
06:01:23 INFO - TinderboxPrint: I/O read bytes / time<br/>4,128,768 / 0
06:01:23 INFO - TinderboxPrint: I/O write bytes / time<br/>0 / 0
06:01:23 INFO - TinderboxPrint: CPU idle<br/>3.8 (94.5%)
06:01:23 INFO - TinderboxPrint: CPU system<br/>0.1 (3.2%)
06:01:23 INFO - TinderboxPrint: CPU user<br/>0.1 (2.0%)
06:01:23 INFO - TinderboxPrint: Swap in / out<br/>0 / 0
06:01:23 INFO - verify-device - Wall time: 1s; CPU: 5.0%; Read bytes: 4128768; Write bytes: 0; Read time: 0; Write time: 0

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Component: Applications: MozharnessCore → Autophone
Product: Release Engineering → Testing
QA Contact: jlund

CosmisS: This certainly looks like a dupe of bug 1504757. Why did you un-dupe it?

Flags: needinfo?(csabou)

After messing up with bug 1532504 wanted to be cautious but yeah every log points to bug 1504757.

Status: REOPENED → RESOLVED
Closed: 5 years ago5 years ago
Flags: needinfo?(csabou)
Resolution: --- → DUPLICATE
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.