From c39afbd5fcdfff2ad5e7f6963768da9f3d8027d2 Mon Sep 17 00:00:00 2001 From: Slawek Kaplonski Date: Mon, 22 Oct 2018 22:58:48 +0200 Subject: [PATCH] [Functional] Increase test_timeout for db migration tests Patch [1] increased timeouts for test_walk_version functional tests for MySQL backend to 300 seconds to avoid failures due to timeouts. Unfortunately it looks that on nodes from some cloud providers used in the gate and with number of migration scripts which we have in Neutron those tests can take sometimes even around 400 seconds. So lets increase this to 600 seconds to avoid such failures of functional tests job. [1] https://review.openstack.org/#/c/610003/ Change-Id: I9d129f0e90a072ec980aadabb2c6b812c08e1618 Closes-Bug: #1687027 --- neutron/tests/functional/db/test_migrations.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/neutron/tests/functional/db/test_migrations.py b/neutron/tests/functional/db/test_migrations.py index baca2a28b15..ccf2e4aac61 100644 --- a/neutron/tests/functional/db/test_migrations.py +++ b/neutron/tests/functional/db/test_migrations.py @@ -586,7 +586,7 @@ class TestWalkMigrationsMysql(testlib_api.MySQLTestCaseMixin, # secs having Mitaka set of migrations. 'pymysql' works much slower # on slow nodes than 'psycopg2' and because of that this increased # timeout is required only when for testing with 'mysql' backend. - @test_base.set_timeout(300) + @test_base.set_timeout(600) def test_walk_versions(self): super(TestWalkMigrationsMysql, self).test_walk_versions()