Closed Bug 805801 Opened 13 years ago Closed 13 years ago

[B2G] Marionette problem causing the test to fail

Categories

(Remote Protocol :: Marionette, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: zcampbell, Unassigned)

References

Details

This test started failing on yesterday's build with a marionette problem. The session does not seem to be able to recover after this point and following tests fails. I haven't been able to debug it any further, sorry. Here's a stack trace excluding the teardown: starting httpd running webserver on http://10.246.29.45:40460/ TEST-START test_camera.py test_capture_a_photo (test_camera.TestCamera) ... ok test_capture_a_video (test_camera.TestCamera) ... ERROR ERROR ====================================================================== ERROR: test_capture_a_video (test_camera.TestCamera) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/zacdev/Mozilla/gaia-ui-tests/gaiatest/tests/test_camera.py", line 52, in test_capture_a_video self.wait_for_condition(lambda s: s.find_element(*self._video_timer_locator).text == '00:03') File "/home/zacdev/Mozilla/gaia-ui-tests/gaiatest/gaia_test.py", line 159, in wait_for_condition value = method(self.marionette) File "/home/zacdev/Mozilla/gaia-ui-tests/gaiatest/tests/test_camera.py", line 52, in <lambda> self.wait_for_condition(lambda s: s.find_element(*self._video_timer_locator).text == '00:03') File "/home/zacdev/.virtualenvs/gaia-ui-tests/local/lib/python2.7/site-packages/marionette_client-0.5.1-py2.7.egg/marionette/marionette.py", line 412, in find_element response = self._send_message('findElement', 'value', **kwargs) File "/home/zacdev/.virtualenvs/gaia-ui-tests/local/lib/python2.7/site-packages/marionette_client-0.5.1-py2.7.egg/marionette/marionette.py", line 183, in _send_message self._handle_error(response) File "/home/zacdev/.virtualenvs/gaia-ui-tests/local/lib/python2.7/site-packages/marionette_client-0.5.1-py2.7.egg/marionette/marionette.py", line 241, in _handle_error raise MarionetteException(message=response, status=500) TEST-UNEXPECTED-FAIL : MarionetteException: {u'message': u'error occurred while processing \'findElement\' request: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMessageSender.sendAsyncMessage]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://marionette/content/marionette-actors.js :: MDA_sendAsync :: line 188" data: no]', u'from': u'conn19.marionette1', u'error': u'unknownError'} ======================================================================
This error could occur because the target app (Camera, in this case) has crashed. Can you verify that's not the case?
Yes I think you're right, it's crashing manually for me. This affects the CI run because the tests that run afterwards fail with the same error. Can we change the tearDown somehow to cope with this and recover for future tests?
I can't reproduce this problem, but this test no longer causes the camera app to crash. I think this is possibly still a problem, but don't know how to reproduce. Are there any tests that currently cause app crashes reliably?
I haven't seen this failure lately but as we're only really testing 3-4 apps at the moment.
Zac, can we close this? Any new/current information which would have us leave this open?
Closing, haven't seen this error for a long time.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.