772249 - Marionette hangs at new_session after restarting B2G for mochitests

Status: RESOLVED WORKSFORME

(Remote Protocol :: Marionette, defect)

Description

[Jonathan Griffin (:jgriffin)]

When running mochitests on a B2G emulator, we restart B2G with a test profile.  After this, we use Marionette to navigate to the test page.

Sometime between June 26 and now, this stopped working; the request for new_session after B2G restarts times out:

INFO | runtests.py | Received unexpected exception while running application
Traceback (most recent call last):
  File "/home/jgriffin/armB2G/objdir-gecko/_tests/testing/mochitest/runtests.py", line 697, in runTests
    timeout = timeout)
  File "/home/jgriffin/armB2G/objdir-gecko/_tests/testing/mochitest/automation.py", line 900, in runApp
    stderr = subprocess.STDOUT)
  File "/home/jgriffin/armB2G/objdir-gecko/_tests/testing/mochitest/b2gautomation.py", line 208, in Process
    session = self.marionette.start_session()
  File "/home/jgriffin/mozilla-central/src/testing/marionette/client/marionette/marionette.py", line 220, in start_session
    self.session = self._send_message('newSession', 'value')
  File "/home/jgriffin/mozilla-central/src/testing/marionette/client/marionette/marionette.py", line 142, in _send_message
    raise TimeoutException(message='socket.timeout', status=ErrorCodes.TIMEOUT, stacktrace=None)
TimeoutException: socket.timeout

Comment 1

[Jonathan Griffin (:jgriffin)]

This is caused by bug 772307; that bug prevents shell.js from creating the content frame, which prevents Marionette from loading a listener frame script, which causes new_session to fail.

Comment 2

[Jonathan Griffin (:jgriffin)]

So, I can't test this on emulators currently due to https://github.com/mozilla-b2g/B2G/issues/70.  I tried this on an otoro device, and the problem still persists.  The only error in logcat that looks relevant is:

E/GeckoConsole(  106): [JavaScript Error: "NS_ERROR_MALFORMED_URI: Component returned failure code: 0x804b000a (NS_ERROR_MALFORMED_URI) [nsIIOService2.newURI]" {file: "chrome://browser/content/shell.js" line: 59}]

However, this same error was observed last week on the emulator (before it broke) and there it did not block reftest from running, so it may not be the cause of this problem on the otoro device.

Comment 3

[Jonathan Griffin (:jgriffin)]

This doesn't seem to be happening any longer.