Closed Bug 814481 Opened 12 years ago Closed 12 years ago

Intermittent robocop "DMError: Invalid process line: ." or "DMError: Invalid process line: Test results for FennecInstrumentationTestRunner=.F"

Categories

(Testing :: Mochitest, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emorley, Assigned: gbrown)

References

Details

(Keywords: intermittent-failure)

Android no-ionmonkey Tegra 250 mozilla-inbound opt test robocop on 2012-11-21 23:04:40 PST for push 60b5863c9eed slave: tegra-177 https://tbpl.mozilla.org/php/getParsedLog.php?id=17269640&tree=Mozilla-Inbound { INFO | runtests.py | Running tests: start. FIRE PROC: '"MOZ_CRASHREPORTER=1,XPCOM_DEBUG_BREAK=stack,MOZ_CRASHREPORTER_NO_REPORT=1,NO_EM_RESTART=1,MOZ_PROCESS_LOG=/tmp/tmpmOU2F_pidlog,XPCOM_MEM_BLOAT_LOG=/mnt/sdcard/tests/profile/runtests_leaks.log" am instrument -w -e deviceroot /mnt/sdcard/tests -e class org.mozilla.fennec.tests.testBookmarklets org.mozilla.roboexample.test/org.mozilla.fennec.FennecInstrumentationTestRunner' ERROR: Unable to parse process list (bug 805969) Line: Test results for FennecInstrumentationTestRunner=. Full output of process list: Test results for FennecInstrumentationTestRunner=. Time: 49.587 OK (1 test) 10031 1507 com.mozilla.SUTAgentAndroid 10007 1200 com.android.inputmethod.latin 1001 1212 com.android.phone 1000 1020 system 10026 1605 com.svox.pico 10028 1591 com.android.defcontainer 10029 1348 com.android.deskclock 10034 1532 org.mozilla.ffxcp 10018 1217 com.android.launcher 10013 1480 com.cooliris.media 10004 1413 android.process.media 10009 1459 com.android.quicksearchbox 10002 1472 com.android.music 10032 1449 com.mozilla.watcher 10006 1430 com.android.mms 10010 1404 com.android.providers.calendar 10014 1366 com.android.email 10017 1358 com.android.bluetooth 10015 1257 android.process.acore 1000 1229 com.android.settings INFO | runtests.py | Received unexpected exception while running application Traceback (most recent call last): File "/builds/tegra-177/test/build/tests/mochitest/runtests.py", line 731, in runTests timeout = timeout) File "/builds/tegra-177/test/build/tests/mochitest/automation.py", line 1051, in runApp stderr = subprocess.STDOUT) File "/builds/tegra-177/test/build/tests/mochitest/remoteautomation.py", line 133, in Process return self.RProcess(self._devicemanager, cmd, stdout, stderr, env, cwd) File "/builds/tegra-177/test/build/tests/mochitest/remoteautomation.py", line 143, in __init__ self.proc = dm.launchProcess(cmd, stdout, cwd, env, True) File "/builds/tegra-177/test/build/tests/mochitest/devicemanagerSUT.py", line 524, in launchProcess self.fireProcess(cmdline, failIfRunning) File "/builds/tegra-177/test/build/tests/mochitest/devicemanagerSUT.py", line 491, in fireProcess pid = self.processExist(appname) File "/builds/tegra-177/test/build/tests/mochitest/devicemanager.py", line 177, in processExist procList = self.getProcessList() File "/builds/tegra-177/test/build/tests/mochitest/devicemanagerSUT.py", line 465, in getProcessList raise DMError("Invalid process line: %s" % line) DMError: Invalid process line: Test results for FennecInstrumentationTestRunner=. WARNING | automationutils.processLeakLog() | refcount logging is off, so leaks can't be detected! INFO | runtests.py | Running tests: end. removing file: /mnt/sdcard/tests/logs/mochitest.log Warning: cleaning up pidfile '/builds/tegra-177/test/../runtestsremote.pid' was unsuccessful from the test harness ERROR: runTests() exited with code 1 }
Similar: https://tbpl.mozilla.org/php/getParsedLog.php?id=17261919&tree=Mozilla-Inbound { INFO | runtests.py | Received unexpected exception while running application Traceback (most recent call last): File "/builds/tegra-261/test/build/tests/mochitest/runtests.py", line 731, in runTests timeout = timeout) File "/builds/tegra-261/test/build/tests/mochitest/automation.py", line 1051, in runApp stderr = subprocess.STDOUT) File "/builds/tegra-261/test/build/tests/mochitest/remoteautomation.py", line 133, in Process return self.RProcess(self._devicemanager, cmd, stdout, stderr, env, cwd) File "/builds/tegra-261/test/build/tests/mochitest/remoteautomation.py", line 143, in __init__ self.proc = dm.launchProcess(cmd, stdout, cwd, env, True) File "/builds/tegra-261/test/build/tests/mochitest/devicemanagerSUT.py", line 524, in launchProcess self.fireProcess(cmdline, failIfRunning) File "/builds/tegra-261/test/build/tests/mochitest/devicemanagerSUT.py", line 491, in fireProcess pid = self.processExist(appname) File "/builds/tegra-261/test/build/tests/mochitest/devicemanager.py", line 177, in processExist procList = self.getProcessList() File "/builds/tegra-261/test/build/tests/mochitest/devicemanagerSUT.py", line 465, in getProcessList raise DMError("Invalid process line: %s" % line) DMError: Invalid process line: . }
Assignee: nobody → gbrown
Depends on: 814496
Depends on: 816581
Summary: Intermittent robocop "DMError: Invalid process line: Test results for FennecInstrumentationTestRunner=." → Intermittent robocop "DMError: Invalid process line: ." or "DMError: Invalid process line: Test results for FennecInstrumentationTestRunner=."
Summary: Intermittent robocop "DMError: Invalid process line: ." or "DMError: Invalid process line: Test results for FennecInstrumentationTestRunner=." → Intermittent robocop "DMError: Invalid process line: ." or "DMError: Invalid process line: Test results for FennecInstrumentationTestRunner=.F"
Bug 814496 landed but doesn't seem to have helped. Geoff, any ideas? Debugging output is: { 28 INFO TEST-START | Shutdown 29 INFO Passed: 25 30 INFO Failed: 0 31 INFO Todo: 0 32 INFO SimpleTest FINISHED ERROR: Unable to parse process list (bug 805969) Line: . Full output of process list: . Test results for FennecInstrumentationTestRunner=. Time: 52.654 OK (1 test) }
Bug 814496 affected sutAgent, which has not yet been updated in production. sutAgent 1.15 deployment is in the works, but is probably another week away.
(In reply to Geoff Brown [:gbrown] from comment #41) > Bug 814496 affected sutAgent, which has not yet been updated in production. > sutAgent 1.15 deployment is in the works, but is probably another week away. Ah; I didn't realise - thank you :-)
Bug 814496 should be deployed now aiui.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.