Closed
Bug 1005837
Opened 10 years ago
Closed 10 years ago
WSAEINVAL (JSbridge) disconnect after testFlash_SWFVideoURL\test1.js on Windows nodes
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect)
Mozilla QA Graveyard
Mozmill Tests
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 915563
People
(Reporter: andrei, Unassigned)
Details
(Keywords: intermittent-failure)
We've had 3 instances: mm-win-vista-32-2 http://mm-ci-master.qa.scl3.mozilla.com:8080/job/mozilla-central_endurance/7657/ http://mozmill-daily.blargon7.com/#/endurance/report/0bd22723d1fdbb446269f765b90816c9 mm-win-vista-32-1 http://mm-ci-master.qa.scl3.mozilla.com:8080/job/mozilla-central_endurance/7667/ http://mozmill-daily.blargon7.com/#/endurance/report/0bd22723d1fdbb446269f765b91ebc35 mm-win-xp-32-2 http://mm-ci-master.qa.scl3.mozilla.com:8080/job/mozilla-central_endurance/7682/ http://mozmill-daily.blargon7.com/#/endurance/report/0bd22723d1fdbb446269f765b90816c9 Relevant log: > 09:28:15 TEST-END | testFlash_SWFVideoURL\test1.js | finished in 631109ms > 09:28:20 RESULTS | Passed: 9 > 09:28:20 RESULTS | Failed: 0 > 09:28:20 RESULTS | Skipped: 1 > 09:28:21 Report document created at 'http://mozauto.iriscouch.com/mozmill-daily/0bd22723d1fdbb446269f765b9382431' > 09:28:21 *** Removing profile: c:\jenkins\workspace\mozilla-central_endurance\data\profile > 09:28:22 *** Uninstalling build: c:\jenkins\workspace\mozilla-central_endurance\data\binary\2014-05-04-03-02-05-mozilla-central-firefox-32 > 09:28:23 *** Removing test repository 'c:\jenkins\workspace\mozilla-central_endurance\data\mozmill-tests' > 09:28:28 Traceback (most recent call last): > 09:28:28 File "c:\jenkins\workspace\mozilla-central_endurance\mozmill-env-windows\python\lib\site-packages\mozmill_automation\testrun.py", line 351, in run > 09:28:28 self.run_tests() > 09:28:28 File "c:\jenkins\workspace\mozilla-central_endurance\mozmill-env-windows\python\lib\site-packages\mozmill_automation\testrun.py", line 557, in run_tests > 09:28:28 TestRun.run_tests(self) > 09:28:28 File "c:\jenkins\workspace\mozilla-central_endurance\mozmill-env-windows\python\lib\site-packages\mozmill_automation\testrun.py", line 302, in run_tests > 09:28:28 self._mozmill.run(tests, self.options.restart) > 09:28:28 File "c:\jenkins\workspace\mozilla-central_endurance\mozmill-env-windows\python\lib\site-packages\mozmill\__init__.py", line 429, in run > 09:28:28 frame = self.run_test_file(frame or self.start_runner(), > 09:28:28 File "c:\jenkins\workspace\mozilla-central_endurance\mozmill-env-windows\python\lib\site-packages\mozmill\__init__.py", line 338, in start_runner > 09:28:28 self.create_network() > 09:28:28 File "c:\jenkins\workspace\mozilla-central_endurance\mozmill-env-windows\python\lib\site-packages\mozmill\__init__.py", line 298, in create_network > 09:28:28 self.jsbridge_port) > 09:28:28 File "c:\jenkins\workspace\mozilla-central_endurance\mozmill-env-windows\python\lib\site-packages\jsbridge\__init__.py", line 47, in wait_and_create_network > 09:28:28 back_channel, bridge = create_network(host, port) > 09:28:28 File "c:\jenkins\workspace\mozilla-central_endurance\mozmill-env-windows\python\lib\site-packages\jsbridge\network.py", line 295, in create_network > 09:28:28 back_channel = BackChannel(hostname, port) > 09:28:28 File "c:\jenkins\workspace\mozilla-central_endurance\mozmill-env-windows\python\lib\site-packages\jsbridge\network.py", line 250, in __init__ > 09:28:28 Bridge.__init__(self, host, port) > 09:28:28 File "c:\jenkins\workspace\mozilla-central_endurance\mozmill-env-windows\python\lib\site-packages\jsbridge\network.py", line 151, in __init__ > 09:28:28 self.connect((host, port)) > 09:28:28 File "c:\jenkins\workspace\mozilla-central_endurance\mozmill-env-windows\python\Lib\asyncore.py", line 356, in connect > 09:28:28 raise socket.error(err, errorcode[err]) > 09:28:28 error: [Errno 10022] WSAEINVAL *Not sure if the component is correct since this might not be mozmill-tests fault, but flash. I'm checking the machines for any relevant info in their logs.
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•10 years ago
|
||
Well it might be a duplicate of bug 915563. I've marked it separately because of the identical failures and because they failed after running the same flash test.
Updated•5 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•