live server tests

170 views
Skip to first unread message

Larry Martell

unread,
Nov 14, 2014, 1:42:22 PM11/14/14
to django...@googlegroups.com
I have a suite of selenium live server tests that have been running
fine (django 1.6, python 2.7, centos 6.5). The host they were running
on died and I moved them to a new host. They are failing there with:

ERROR: setUpClass
----------------------------------------------------------------------
Traceback (most recent call last):
File "/usr/local/motor/motor/app/cdsem/tests/testEventsTableLive.py",
line 25, in setUpClass
cls.selenium = WebDriver()
File "/usr/lib/python2.6/site-packages/selenium/webdriver/firefox/webdriver.py",
line 59, in __init__
self.binary, timeout),
File "/usr/lib/python2.6/site-packages/selenium/webdriver/firefox/extension_connection.py",
line 47, in __init__
self.binary.launch_browser(self.profile)
File "/usr/lib/python2.6/site-packages/selenium/webdriver/firefox/firefox_binary.py",
line 66, in launch_browser
self._wait_until_connectable()
File "/usr/lib/python2.6/site-packages/selenium/webdriver/firefox/firefox_binary.py",
line 100, in _wait_until_connectable
raise WebDriverException("The browser appears to have exited "
WebDriverException: Message: The browser appears to have exited before
we could connect. If you specified a log_file in the FirefoxBinary
constructor, check it for details.

The old box was running Firefox 24.3.0 and the new one is running
31.2.0. Could that have anything to do with it? Anyone ever seen this
and/or know what I can do to fix it?

Larry Martell

unread,
Nov 14, 2014, 2:45:57 PM11/14/14
to django...@googlegroups.com
Well I was able to downgrade FF to 31.1.0 and the live tests are
working now. So the problem is fixed ... at least for
now - until I can't get that version anymore .. so I guess I do need
to figure out why it's failing with 31.2.0 ... or maybe wait until the
next version comes out and see if it still fails there.

Carl Meyer

unread,
Nov 15, 2014, 10:29:41 AM11/15/14
to django...@googlegroups.com
Hi Larry,
Often in the past when a new FF version breaks Selenium, there is very
shortly a new version of the Python Selenium driver that fixes the
issues. (The maintainer of that driver works for Mozilla, so...) So you
might see whether `pip install -U selenium` helps. (And if it doesn't
now, it probably will before long.)

Carl

signature.asc

Larry Martell

unread,
Nov 15, 2014, 4:07:40 PM11/15/14
to django...@googlegroups.com
Updating Selenium did not fix the problem with 31.2.0, but thanks very
much for the tip.
Reply all
Reply to author
Forward
0 new messages