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 protected]> 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 ** Changed in: horizon Status: In Progress => Fix Released -- 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/1592349 Title: Page timeout in selenium integration tests is too small Status in OpenStack Dashboard (Horizon): Fix Released Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1592349/+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
