From fdefb0e7bd14d44608c3c1939865caacfd5dc28c Mon Sep 17 00:00:00 2001 From: Goutham Pacha Ravi Date: Fri, 17 May 2019 10:47:13 -0700 Subject: [PATCH] [CI] Bump timeout for the migrations test case We face slow nodes on the CI, and tests are timing out with a sqllite backend in the gate. Change-Id: I284b48facf633f54aa5a7ec024a1662a1d164daf --- manila/tests/db/migrations/alembic/test_migration.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/manila/tests/db/migrations/alembic/test_migration.py b/manila/tests/db/migrations/alembic/test_migration.py index 32aa0e3a2e..29c40f9b07 100644 --- a/manila/tests/db/migrations/alembic/test_migration.py +++ b/manila/tests/db/migrations/alembic/test_migration.py @@ -139,13 +139,13 @@ class ManilaMigrationsCheckers(test_migrations.WalkVersionsMixin, 'exception': e}) raise - # NOTE(vponomaryov): set 7 minutes timeout for case of running it on + # NOTE(vponomaryov): set 10 minutes timeout for case of running it on # very slow nodes/VMs. Note, that this test becomes slower with each # addition of new DB migration. On fast nodes it can take about 5-10 secs # having Mitaka set of migrations. # 'pymysql' works much slower on slow nodes than 'psycopg2'. And such # timeout mostly required for testing of 'mysql' backend. - @test_utils.set_timeout(420) + @test_utils.set_timeout(600) def test_walk_versions(self): """Walks all version scripts for each tested database.