commit 79c12f5930ecdbacf33fabcba7dce1f4cb8f72ba
Author: Goutham Pacha Ravi <email address hidden>
Date: Tue Mar 12 08:21:42 2019 -0700
Bump timeout on sqlalchemy migration test
As we add more migrations in the database, the
time taken by the test increases. The test
`manila.tests.db.migrations.alembic.
test_migration.TestManilaMigrationsPostgreSQL.test_walk_versions`
runs upgrades, downgrades and database checks for
every migration. It has been timing out on numerous
occasions because it can't run under 5 minutes.
We feel the pinch of the timeouts because
the test itself is run as part of multiple
jobs (ex: unit test jobs on py2x, py3x, coverage,
requirements/lower-constraints check) and
can fail anywhere because it was running
on a "slow" node.
Reviewed: https:/ /review. openstack. org/642788 /git.openstack. org/cgit/ openstack/ manila/ commit/ ?id=79c12f5930e cdbacf33fabcba7 dce1f4cb8f72ba
Committed: https:/
Submitter: Zuul
Branch: master
commit 79c12f5930ecdba cf33fabcba7dce1 f4cb8f72ba
Author: Goutham Pacha Ravi <email address hidden>
Date: Tue Mar 12 08:21:42 2019 -0700
Bump timeout on sqlalchemy migration test
As we add more migrations in the database, the tests.db. migrations. alembic. migration. TestManilaMigra tionsPostgreSQL .test_walk_ versions`
time taken by the test increases. The test
`manila.
test_
runs upgrades, downgrades and database checks for
every migration. It has been timing out on numerous
occasions because it can't run under 5 minutes.
We feel the pinch of the timeouts because s/lower- constraints check) and
the test itself is run as part of multiple
jobs (ex: unit test jobs on py2x, py3x, coverage,
requirement
can fail anywhere because it was running
on a "slow" node.
Change-Id: I1fdef6e9071106 81cb5ffb59f6f90 f8eb67f118b
Partial-Bug: #1793364