Public bug reported: The recent update of Firefox 36, available now on Ubuntu Trusty used on the gate, broke selenium and all gate-horizon-dsvm-integration are failing with errors like: WebDriverException: Message: Can't load the profile. Profile Dir: %s If you specified a log_file in the FirefoxBinary constructor, check it for details.
See for example: http://logs.openstack.org/60/157760/4/check/gate- horizon-dsvm-integration/fd3c268/console.html A new version of Selenium has not been released yet. See the Selenium bug: https://code.google.com/p/selenium/issues/detail?id=8399). I think this should be solved on infrastructural level (pinning firefox version, for example). After some IRC discussion it seems it's not the solution which is going to be implemented, and the job will be non-voting instead. This means that people can't rely on at all on results from that test (they are not even starting) until the new selenium pip packages are available, and we could suffer from unexpected issues when the tests are reenabled because of some patch which seemed to work locally but not on the gate. That said, who codes decides. ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1426071 Title: horizon integration tests are currently broken in Firefox 36 Status in OpenStack Dashboard (Horizon): New Bug description: The recent update of Firefox 36, available now on Ubuntu Trusty used on the gate, broke selenium and all gate-horizon-dsvm-integration are failing with errors like: WebDriverException: Message: Can't load the profile. Profile Dir: %s If you specified a log_file in the FirefoxBinary constructor, check it for details. See for example: http://logs.openstack.org/60/157760/4/check/gate- horizon-dsvm-integration/fd3c268/console.html A new version of Selenium has not been released yet. See the Selenium bug: https://code.google.com/p/selenium/issues/detail?id=8399). I think this should be solved on infrastructural level (pinning firefox version, for example). After some IRC discussion it seems it's not the solution which is going to be implemented, and the job will be non-voting instead. This means that people can't rely on at all on results from that test (they are not even starting) until the new selenium pip packages are available, and we could suffer from unexpected issues when the tests are reenabled because of some patch which seemed to work locally but not on the gate. That said, who codes decides. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1426071/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
