search

mozilla / mozmill-ci

[OBSOLETE] Mozmill CI system driven by Mozilla Pulse and Jenkins
https://wiki.mozilla.org/QA/Automation/Projects/Mozmill_Automation/Mozmill_CI
19 stars 18 forks source link

Windows 7 machine fails with "Sorry, cannot connect to jsbridge extension, port 57655" #100

Closed whimboo closed 12 years ago

whimboo commented 12 years ago

Nearly all the tests are failing on the windows 7 machine with:

http://qa-masterblaster.mv.mozilla.com:8080/job/mozilla-central_remote/174/console

346 files updated, 0 files merged, 0 files removed, 0 files unresolved * Installing 2012-05-25-11-32-55-mozilla-central-firefox-15.0a1.en-US.win32.installer.exe => c:\users\mozilla\appdata\local\temp\tmpdcavap.binary\ * Updating to branch 'default' pulling from mozmill-tests searching for changes no changes found 0 files updated, 0 files merged, 0 files removed, 0 files unresolved Sorry, cannot connect to jsbridge extension, port 57655 * Uninstalling c:\users\mozilla\appdata\local\temp\tmpdcavap.binary\ * Removing repository 'c:\users\mozilla\appdata\local\temp\tmp7u8bow.mozmill-tests' Recording test results No test report files were found. Configuration error? Build step 'Publish JUnit test result report' changed build result to FAILURE

Not sure why we cannot connect. Dave would you mind checking if it is still the case? Are no ports available or why can't jsbridge connect to the self-chosen ports? I don't want to restart this box because I think it will make the failure go away.

davehunt commented 12 years ago

This appears to be somewhat intermittent, but it is still occurring. See http://qa-masterblaster.mv.mozilla.com:8080/computer/windows-7_32_01/builds for history of builds this node has completed. Unfortunately I can't tell what ports successful jobs were running on as we don't output this.

I had a quick look at the output from netstat -an and there didn't appear to be anything running on ports mentioned in recently failed builds.

whimboo commented 12 years ago

Have you tried to execute a testrun manually? Would be good to know if it can even be reproduced outside of Jenkins.

davehunt commented 12 years ago

I didn't try to execute manually, do you mean on the VM using the --port command line option? I cannot see any recent failures of this kind.

whimboo commented 12 years ago

No, just the testrun script without the --port. We don't make use of it yet in CI. If that would fail too, it would be a good indicator.

Given that it doesn't happen anymore lets close the issue for now and reopen if it reappears.