975986 - Mozmill fails to connect to jsbridge

Status: RESOLVED WONTFIX

(Testing Graveyard :: Mozmill, defect)

Description

[Cosmin Malutan, [:cosmin-malutan]]

Attachment: jenkins_log

This happens from time to time when running testruns via CI. 
As a difference between this and usual disconnects is that here we fail to make even a first connection, so we don't run any test at all.
My guess is that here mozmill doesn't start at all, given that the couchdb response says we don't have an "application_id".

Also I should mention this happens across all platforms.

>01:17:09 RESULTS | Passed: 0
>01:17:09 RESULTS | Failed: 0
>01:17:09 RESULTS | Skipped: 0
>01:17:09 Traceback (most recent call last):
>01:17:09   File "/home/mozauto/jenkins/workspace/mozilla-esr24_endurance/mozmill-env-linux/python-lib/mozmill_automation/testrun.py", line 349, in run
>01:17:09     self.run_tests()
>01:17:09   File "/home/mozauto/jenkins/workspace/mozilla-esr24_endurance/mozmill-env-linux/python-lib/mozmill_automation/testrun.py", line 555, in run_tests
>01:17:09     TestRun.run_tests(self)
>01:17:09   File "/home/mozauto/jenkins/workspace/mozilla-esr24_endurance/mozmill-env-linux/python-lib/mozmill_automation/testrun.py", line 300, in run_tests
>01:17:09     self._mozmill.run(tests, self.options.restart)
>01:17:09   File "/home/mozauto/jenkins/workspace/mozilla-esr24_endurance/mozmill-env-linux/python-lib/mozmill/__init__.py", line 411, in run
>01:17:09     frame = self.run_test_file(frame or self.start_runner(),
>01:17:09   File "/home/mozauto/jenkins/workspace/mozilla-esr24_endurance/mozmill-env-linux/python-lib/mozmill/__init__.py", line 327, in start_runner
>01:17:09     self.create_network()
>01:17:09   File "/home/mozauto/jenkins/workspace/mozilla-esr24_endurance/mozmill-env-linux/python-lib/mozmill/__init__.py", line 287, in create_network
>01:17:09     self.jsbridge_port)
>01:17:09   File "/home/mozauto/jenkins/workspace/mozilla-esr24_endurance/mozmill-env-linux/python-lib/jsbridge/__init__.py", line 45, in wait_and_create_network
>01:17:09     raise Exception("Cannot connect to jsbridge extension, port %s" % port)
>01:17:09 Exception: Cannot connect to jsbridge extension, port 56197
>01:17:09 Sending results to 'http://mozauto.iriscouch.com/mozmill-daily/' failed (This document requires the field application_id).
>01:17:09 *** Removing profile: /home/mozauto/jenkins/workspace/mozilla-esr24_endurance/data/profile

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+2]]

This most likely might be a networking issue or a broken behavior in Firefox. Have you re-run those affected builds in CI to check if a second run succeeds? If not please do so. We would need a reliable testcase to reproduce it.

Comment 2

[Cosmin Malutan, [:cosmin-malutan]]

From what I remember it works second time we retrigger the job for the CI instance.
Also it failed with this consecutively when we tried to ran metro testruns on our vms, the issue that we didn't see on a clean vm, and I can see this every time when running testruns on a tablet pc.

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Tablet PC in terms of a Surface tablet? Please give detailed STR how to reproduce it and I will try myself.

Comment 4

[Cosmin Malutan, [:cosmin-malutan]]

Attachment: jenkins_log windows

About this failure on a tablet:
- It was on an Acer Iconia W3
- I started an mozmill-ci server 
- I connected the tabled as an slave node
- I triggered metro testruns on it.

This failed on windows xp x86 mm-win-xp-32-1 with wsaeinval, in the same place.
Attached is the log.

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Would you mind to test with a debug build? Do you get any assertion or crash?

Comment 6

[Henrik Skupin [:whimboo][⌚️UTC+2]]

We are not going back to use Mozmill for our UI testing of Firefox and this is doesn't look like a real blocker for a possible release.