Closed Bug 869144 Opened 12 years ago Closed 12 years ago

Intermittent b2g test_api.js,test_eval-04.js,test_bug794211.js,test_base64_vlq.js,test_lowMinutes.js | test failed (with xpcshell return code: -1) after "DMError: Timeout exceeded for shell call"

Categories

(DevTools :: Debugger, defect)

Product:
DevTools
Component:
Debugger
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(firefox25 wontfix, firefox26 fixed, firefox-esr24 wontfix)

Status:
RESOLVED FIXED
Milestone:
Firefox 26
Tracking Flags:
Tracking Status
firefox25 --- wontfix
firefox26 --- fixed
firefox-esr24 --- wontfix

People

(Reporter: RyanVM, Assigned: vporof)

References

Details

(Keywords: intermittent-failure)

https://tbpl.mozilla.org/php/getParsedLog.php?id=22632906&tree=Mozilla-Inbound b2g_ics_armv7a_gecko_emulator_vm mozilla-inbound opt test xpcshell on 2013-05-06 06:55:34 PDT for push 8e98863ce994 slave: tst-linux64-ec2-073 07:14:47 INFO - TEST-INFO | /builds/slave/test/build/tests/xpcshell/tests/toolkit/devtools/sourcemap/tests/unit/test_api.js | running test ... 07:19:47 WARNING - TEST-UNEXPECTED-FAIL | /builds/slave/test/build/tests/xpcshell/tests/toolkit/devtools/sourcemap/tests/unit/test_api.js | test failed (with xpcshell return code: -1), see following log: 07:19:47 INFO - >>>>>>> 07:19:47 INFO - Traceback (most recent call last): 07:19:47 INFO - File "runtestsb2g.py", line 64, in launchProcess 07:19:47 INFO - outputFile = XPCShellRemote.launchProcess(self, cmd, stdout, stderr, env, cwd) 07:19:47 INFO - File "/builds/slave/test/build/tests/xpcshell/remotexpcshelltests.py", line 309, in launchProcess 07:19:47 INFO - self.shellReturnCode = self.device.shell(cmd, f) 07:19:47 INFO - File "/builds/slave/test/build/venv/local/lib/python2.7/site-packages/mozdevice/devicemanagerADB.py", line 138, in shell 07:19:47 INFO - raise DMError("Timeout exceeded for shell call") 07:19:47 INFO - DMError: Timeout exceeded for shell call 07:19:47 INFO - <<<<<<<
https://tbpl.mozilla.org/php/getParsedLog.php?id=22964761&tree=Mozilla-Inbound
Summary: Intermittent b2g toolkit/devtools/sourcemap/tests/unit/test_api.js | test failed (with xpcshell return code: -1) after "DMError: Timeout exceeded for shell call" → Intermittent b2g test_api.js,test_eval-04.js | test failed (with xpcshell return code: -1) after "DMError: Timeout exceeded for shell call"
https://tbpl.mozilla.org/php/getParsedLog.php?id=23601025&tree=Birch
Summary: Intermittent b2g test_api.js,test_eval-04.js | test failed (with xpcshell return code: -1) after "DMError: Timeout exceeded for shell call" → Intermittent b2g test_api.js,test_eval-04.js,test_bug794211.js | test failed (with xpcshell return code: -1) after "DMError: Timeout exceeded for shell call"
https://tbpl.mozilla.org/php/getParsedLog.php?id=24346461&tree=Birch
Summary: Intermittent b2g test_api.js,test_eval-04.js,test_bug794211.js | test failed (with xpcshell return code: -1) after "DMError: Timeout exceeded for shell call" → Intermittent b2g test_api.js,test_eval-04.js,test_bug794211.js,test_base64_vlq.js | test failed (with xpcshell return code: -1) after "DMError: Timeout exceeded for shell call"
https://tbpl.mozilla.org/php/getParsedLog.php?id=24788033&tree=Birch Dave, this seems to happen most often in the mozapps/downloads test suite. Any chance you can look at it?
Flags: needinfo?(dtownsend+bugmail)
Summary: Intermittent b2g test_api.js,test_eval-04.js,test_bug794211.js,test_base64_vlq.js | test failed (with xpcshell return code: -1) after "DMError: Timeout exceeded for shell call" → Intermittent b2g test_api.js,test_eval-04.js,test_bug794211.js,test_base64_vlq.js,test_lowMinutes.js | test failed (with xpcshell return code: -1) after "DMError: Timeout exceeded for shell call"
-> Paolo
Flags: needinfo?(dtownsend+bugmail) → needinfo?(paolo.mozmail)
Depends on: 869638
This bug seems to be collapsing several unrelated test timeouts, but we don't have enough information from the test logs. The harness fails with this mysterious "device manager error". I've commented in bug 869638, that I originally thought might've been the reason why we don't get the test logs, but I may have missed some evolutions of the test harness, so waiting for feedback there. If you have any ideas, you're welcome.
Flags: needinfo?(paolo.mozmail)
Depends on: 889317
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Assignee: nobody → vporof
status-firefox25: --- → wontfix
status-firefox26: --- → fixed
status-firefox-esr24: --- → wontfix
Depends on: 876277
Target Milestone: --- → Firefox 26
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.