Closed Bug 1097486 Opened 10 years ago Closed 10 years ago

Mozmill tests failed with the message 'Exception: Sorry, cannot connect to jsbridge extension, port 24242'

Categories

(Thunderbird :: Testing Infrastructure, defect)

Product:
Thunderbird
Component:
Testing Infrastructure
Platform:
All
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: hiro, Unassigned)

Details

(Keywords: intermittent-failure) 

INFO | (runtestlist.py) | Running directory: account
['c:\\slave\\test\\build\\mozmill-virtualenv\\Scripts\\python.exe', 'runtest.py', '-t', 'account', '--binary', 'C:\\slave\\test\\build\\thunderbird\\thunderbird.exe', '--symbols-path', 'symbols']
Using profile dir: C:\slave\test\build\mozmill\mozmillprofile
Traceback (most recent call last):
  File "runtest.py", line 513, in <module>
    ThunderTestCLI().run()
  File "c:\slave\test\build\mozmill-virtualenv\lib\site-packages\mozmill\__init__.py", line 785, in run
    self.mozmill.start(runner=runner, profile=runner.profile)
  File "c:\slave\test\build\mozmill-virtualenv\lib\site-packages\mozmill\__init__.py", line 229, in start
    self.create_network()
  File "c:\slave\test\build\mozmill-virtualenv\lib\site-packages\mozmill\__init__.py", line 203, in create_network
    self.jsbridge_port)
  File "c:\slave\test\build\mozmill-virtualenv\lib\site-packages\jsbridge\__init__.py", line 72, in wait_and_create_network
    raise Exception("Sorry, cannot connect to jsbridge extension, port %s" % port)
Exception: Sorry, cannot connect to jsbridge extension, port 24242
##### MOZMILL-RICH-FAILURES-BEGIN #####
##### MOZMILL-RICH-FAILURES-END #####
TEST-UNEXPECTED-FAIL | (runtestlist.py) | Exited with code 1 during directory run
Summary: Exception: Sorry, cannot connect to jsbridge extension, port 24242 → Mozmill tests failed with the message 'Exception: Sorry, cannot connect to jsbridge extension, port 24242'
Fixed by backout of bug 1084973.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.