Closed
Bug 1297624
Opened 8 years ago
Closed 8 years ago
Intermittent Android reftest Automation Error: Exception caught while running tests
Categories
(Testing :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1157948
People
(Reporter: aryx, Assigned: gbrown)
References
Details
+++ This bug was initially created as a clone of Bug #809753 +++ https://treeherder.mozilla.org/logviewer.html#?job_id=2434097&repo=autoland 07:22:17 INFO - REFTEST TEST-START | http://10.0.2.2:8854/tests/layout/reftests/bugs/218473-1.html == http://10.0.2.2:8854/tests/layout/reftests/bugs/218473-1-ref.html 07:22:17 INFO - REFTEST TEST-LOAD | http://10.0.2.2:8854/tests/layout/reftests/bugs/218473-1.html | 382 / 818 (46%) 07:22:17 INFO - REFTEST TEST-LOAD | http://10.0.2.2:8854/tests/layout/reftests/bugs/218473-1-ref.html | 382 / 818 (46%) 07:22:27 INFO - INFO | automation.py | Application ran for: 0:20:36.667922 07:22:27 INFO - INFO | zombiecheck | Reading PID log: /tmp/tmppjauLApidlog 07:22:27 INFO - /data/anr/traces.txt not found 07:22:27 INFO - WARNING: Unable to retrieve log file (/storage/sdcard/tests/reftest/reftest.log) from remote device 07:22:27 INFO - Automation Error: Exception caught while running tests 07:22:27 INFO - Traceback (most recent call last): 07:22:27 INFO - File "/home/worker/workspace/build/tests/reftest/remotereftest.py", line 422, in runTests 07:22:27 INFO - retVal = reftest.runTests(options.tests, options) 07:22:27 INFO - File "/home/worker/workspace/build/tests/reftest/runreftest.py", line 426, in runTests 07:22:27 INFO - return self.runSerialTests(manifests, options, cmdargs) 07:22:27 INFO - File "/home/worker/workspace/build/tests/reftest/runreftest.py", line 681, in runSerialTests 07:22:27 INFO - debuggerInfo=debuggerInfo) 07:22:27 INFO - File "/home/worker/workspace/build/tests/reftest/remotereftest.py", line 336, in runApp 07:22:27 INFO - timeout=timeout) 07:22:27 INFO - File "/home/worker/workspace/build/tests/reftest/automation.py", line 577, in runApp 07:22:27 INFO - crashed = self.checkForCrashes(os.path.join(profileDir, "minidumps"), symbolsPath) 07:22:27 INFO - File "/home/worker/workspace/build/tests/reftest/remoteautomation.py", line 212, in checkForCrashes 07:22:27 INFO - logcat = self._devicemanager.getLogcat(filterOutRegexps=fennecLogcatFilters) 07:22:27 INFO - File "/home/worker/workspace/build/venv/local/lib/python2.7/site-packages/mozdevice/devicemanager.py", line 166, in getLogcat 07:22:27 INFO - timeout=self.short_timeout) 07:22:27 INFO - File "/home/worker/workspace/build/venv/local/lib/python2.7/site-packages/mozdevice/devicemanager.py", line 405, in shellCheckOutput 07:22:27 INFO - raise DMError("Non-zero return code for command: %s (output: '%s', retval: '%s')" % (cmd, output, retval)) 07:22:27 INFO - DMError: Non-zero return code for command: ['/system/bin/logcat', '-v', 'time', '-d', 'dalvikvm:I', 'ConnectivityService:S', 'WifiMonitor:S', 'WifiStateTracker:S', 'wpa_supplicant:S', 'NetworkStateTracker:S'] (output: '', retval: 'None') 07:24:34 INFO - WARNING: Error getting device information
Assignee | ||
Comment 1•8 years ago
|
||
Emulator became unresponsive, the test harness noticed because logcat failed, harness threw DMError. This has always happened for Android emulator tests. It can happen during any test. On buildbot, the "DMError" triggers an automatic retry; for taskcluster, a solution is being developed in bug 1280570.
Assignee: nobody → gbrown
Status: NEW → RESOLVED
Closed: 8 years ago
Depends on: 1280570
Resolution: --- → DUPLICATE
Updated•8 years ago
|
Keywords: intermittent-failure
You need to log in
before you can comment on or make changes to this bug.
Description
•