Integration test timeouts for instance creation inconsistent

Bug #1281254 reported by Mat Lowery
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Fix Released
Undecided
Mat Lowery

Bug Description

WaitForConfigurationInstanceToFinish.test_instance_with_configuration_active timeout is 7 minutes while WaitForRestoreToFinish.test_instance_restored timeout is 32 minutes. When running on a personal VM, I sometimes hit the 7 minute timeout. Since these are the same operation, they should have the same timeout.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to trove (master)

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

Changed in trove:
assignee: nobody → Mat Lowery (mat-lowery)
status: New → In Progress
Revision history for this message
Denis M. (dmakogon) wrote :

Agreed with Mat. Timeouts should be consistent through all integration tests.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to trove (master)

Reviewed: https://review.openstack.org/74136
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=f26e74701efa8910edd5a5963d7bc962fc8796ef
Submitter: Jenkins
Branch: master

commit f26e74701efa8910edd5a5963d7bc962fc8796ef
Author: Mat Lowery <email address hidden>
Date: Fri Feb 14 22:39:59 2014 -0600

    Use consistent timeouts for integration tests

    Closes-Bug: #1281254
    Change-Id: Ifc16709c68b059b0bf5e6872236970e012ee25bc

Changed in trove:
status: In Progress → Fix Committed
Changed in trove:
milestone: none → icehouse-3
Thierry Carrez (ttx)
Changed in trove:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in trove:
milestone: icehouse-3 → 2014.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.