c0fec67672
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. [1] http://sqlalche.me/e/rvf5 Change-Id: Ie291fda7d23a696aaa1160d126a3cf72b08c522f Related-Bug: #1687027 |
||
|---|---|---|
| .. | ||
| migrations | ||
| __init__.py | ||
| test_ipam.py | ||
| test_migrations.py | ||
| test_models.py | ||
| test_network.py | ||