In some cases our db migration tests which run on MySQL are
failing with timeout and it happens due to slow VMs on which
job is running.
Sometimes it may also happen that timeout exception is raised
in the middle of some sqlalchemy operations and
sqlalchemy.InterfaceError is raised as last one.
Details about this exception can be found in [1].
To avoid many rechecks because of this reason this patch
introduces new decorator which is very similar to "unstable_test"
but will skip test only if one of exceptions mentioned above will
be raised.
In all other cases it will fail test.
That should be a bit more safe for us because we will not miss
some other failures raised in those tests and will avoid rechecks
because of this "well-known" reason described in related bug.
Reviewed: https:/ /review. openstack. org/636892 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=c0fec676723 649a0516cf3d4af 0dccc0fe832095
Committed: https:/
Submitter: Zuul
Branch: master
commit c0fec676723649a 0516cf3d4af0dcc c0fe832095
Author: Slawek Kaplonski <email address hidden>
Date: Thu Feb 14 11:08:19 2019 +0100
Add new test decorator skip_if_timeout
In some cases our db migration tests which run on MySQL are InterfaceError is raised as last one.
failing with timeout and it happens due to slow VMs on which
job is running.
Sometimes it may also happen that timeout exception is raised
in the middle of some sqlalchemy operations and
sqlalchemy.
Details about this exception can be found in [1].
To avoid many rechecks because of this reason this patch
introduces new decorator which is very similar to "unstable_test"
but will skip test only if one of exceptions mentioned above will
be raised.
In all other cases it will fail test.
That should be a bit more safe for us because we will not miss
some other failures raised in those tests and will avoid rechecks
because of this "well-known" reason described in related bug.
[1] http:// sqlalche. me/e/rvf5
Change-Id: Ie291fda7d23a69 6aaa1160d126a3c f72b08c522f
Related-Bug: #1687027