Page timeout in selenium integration tests is too small

[Timur Sufiev]

The default page timeout in selenium integration tests is set to 30 seconds, which is too small for a first couple of tests which are run after Apache in devstack is restarted. It takes around 30 seconds to just log in into Horizon, because a lot of data is fetched into the memory of Apache workers during these first tests, hence they time out and fail.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/329369

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/329369
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=eecb8bfe148cec0bd0afb471b7723fc5c57de4d8
Submitter: Jenkins
Branch: master

commit eecb8bfe148cec0bd0afb471b7723fc5c57de4d8
Author: Timur Sufiev <email address hidden>
Date: Tue Jun 14 13:47:20 2016 +0300

    Change default timeouts in integration tests

    First, increase page_timeout to one minute, which should help in case
    of a first couple of tests waiting for Apache workers to "warm up".

    Second, reduce explicit_wait to 90 seconds (from 5 minutes), because
    if something in Horizon doesn't complete in 90 seconds, then almost
    for sure it won't complete in 5 minutes as well and only will spend
    time, which is limited for integration tests.

    Change-Id: Icb0767146fdb2682dca237ee18bbc4c3c8d976d0
    Closes-Bug: #1592349

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/horizon 10.0.0.0b2 development milestone.