Comment 1 for bug 1481875

Revision history for this message
Liusheng (liusheng) wrote :

It is similar with Gnocchi, I wonder if this test need to create table ? I can run this test OK in my environment with aodh installed and running. the database connection is set with "connection = mysql://root:password@127.0.0.1/aodh?charset=utf8" in aodh.conf

see:

root@monasca:/opt/stack/aodh# python setup.py testr --testr-args aodh.tests.storage.sqlalchemy.test_migrations.ModelsMigrationsSync
running testr
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-600} \
${PYTHON:-python} -m subunit.run discover ${OS_TEST_PATH:-./aodh/tests} -t . --list
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-600} \
${PYTHON:-python} -m subunit.run discover ${OS_TEST_PATH:-./aodh/tests} -t . --load-list /tmp/tmpWau2_I
Ran 1 tests in 0.087s (-0.003s)
PASSED (id=4)
root@monasca:/opt/stack/aodh# vi tox.ini
root@monasca:/opt/stack/aodh# python setup.py testr --slowest --testr-args aodh.tests.storage.sqlalchemy.test_migrations.ModelsMigrationsSync
running testr
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-600} \
${PYTHON:-python} -m subunit.run discover ${OS_TEST_PATH:-./aodh/tests} -t . --list
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-600} \
${PYTHON:-python} -m subunit.run discover ${OS_TEST_PATH:-./aodh/tests} -t . --load-list /tmp/tmpq0HTKu
Ran 1 tests in 0.084s (-0.002s)
PASSED (id=5)
Slowest Tests
Test id Runtime (s)
----------------------------------------------------------------------------------- -----------
aodh.tests.storage.sqlalchemy.test_migrations.ModelsMigrationsSync.test_models_sync 0.082

I will try to find a way to try to make this test run with real backend scenario.