Can confirm, had the same issue locally, was fixed after a downgrade to
selenium 2.48.
Good catch!
Itxaka
On 01/28/2016 10:08 PM, Timur Sufiev wrote:
According to the results at
https://review.openstack.org/#/c/273697/1 capping Selenium to be not
greater than 2.49 fixes broken tests. Patch to global-requirements is
here: https://review.openstack.org/#/c/273750/
On Thu, Jan 28, 2016 at 9:22 PM Timur Sufiev <tsuf...@mirantis.com
<mailto:tsuf...@mirantis.com>> wrote:
Hello, Horizoneers
You may have noticed recent integration tests failures seemingly
unrelated to you patches, with a stacktrace like:
http://paste2.org/2Hk9138U I've already filed a bug for that,
https://bugs.launchpad.net/horizon/+bug/1539197 Appears to be a
Selenium issue, currently investigating it.
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
