Hrm, this is not my homest of home turfs :-/
- tox based test calling (as mentioned upstream) blocks on pip install
- the python3-stestr based test fails to find resources when stripped
This works:
$ pkgos-dh_auto_test --no-py2 "cinder.tests.unit.api.contrib.test_volume_type_encryption.VolumeTypeEncryptionTest.test_create_volume_exists" 2>&1 | tee testlog-3.26.0-2.summary
Looking back I realized you seem to have adapted your Debian rules to call it rather similarly.
This works (and has a bit more unreadable debug data than the other call):
$PYTHON=python3.7 python3-stestr run --subunit "cinder.tests.unit.api.contrib.test_volume_type_encryption.VolumeTypeEncryptionTest.test_create_volume_exists" 2>&1 | tee testlog-3.26.0-2.details
Only in the good case I see this:
/usr/lib/python3/dist-packages/sqlalchemy/orm/evaluator.py:71: SAWarning: Evaluating non-mapped column expression 'updated_at' onto ORM instances; this is a deprecated use
"UPDATE / DELETE expressions." % clause)
Maybe sqlite finally dropped this, but I'm not sure as this is a deprecation warning of python3-sqlalchemy and not sqlite3.
I then modified the test to fail in any case, that will spill more debug in the good case (if the test is good then it will only say ok).
That let me compare the info and warnings in the beginning between good/bad case:
The four INFO/WARNING on keystonemiddleware.auth_token, keystonemiddleware._common.config, keystonemiddleware.auth_token are the same in good and bad case.
The next entry in good case that is missing in the bad case is:
2018-12-07 09:13:42,744 INFO [cinder.rpc] Automatically selected cinder-scheduler objects version 1.37 as minimum service version.
Hrm, this is not my homest of home turfs :-/
- tox based test calling (as mentioned upstream) blocks on pip install
- the python3-stestr based test fails to find resources when stripped
This works: tests.unit. api.contrib. test_volume_ type_encryption .VolumeTypeEncr yptionTest. test_create_ volume_ exists" 2>&1 | tee testlog- 3.26.0- 2.summary
$ pkgos-dh_auto_test --no-py2 "cinder.
Looking back I realized you seem to have adapted your Debian rules to call it rather similarly.
This works (and has a bit more unreadable debug data than the other call):
$PYTHON=python3.7 python3-stestr run --subunit "cinder. tests.unit. api.contrib. test_volume_ type_encryption .VolumeTypeEncr yptionTest. test_create_ volume_ exists" 2>&1 | tee testlog- 3.26.0- 2.details
Only in the good case I see this: python3/ dist-packages/ sqlalchemy/ orm/evaluator. py:71: SAWarning: Evaluating non-mapped column expression 'updated_at' onto ORM instances; this is a deprecated use
/usr/lib/
"UPDATE / DELETE expressions." % clause)
Maybe sqlite finally dropped this, but I'm not sure as this is a deprecation warning of python3-sqlalchemy and not sqlite3.
I then modified the test to fail in any case, that will spill more debug in the good case (if the test is good then it will only say ok).
That let me compare the info and warnings in the beginning between good/bad case: are.auth_ token, keystonemiddlew are._common. config, keystonemiddlew are.auth_ token are the same in good and bad case.
The four INFO/WARNING on keystonemiddlew
The next entry in good case that is missing in the bad case is:
2018-12-07 09:13:42,744 INFO [cinder.rpc] Automatically selected cinder-scheduler objects version 1.37 as minimum service version.