Reviewed: https://review.openstack.org/452678 Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=20a5de74e7fb3a6e973b52e34dbba938b5e3000d Submitter: Jenkins Branch: master
commit 20a5de74e7fb3a6e973b52e34dbba938b5e3000d Author: akhiljain23 <[email protected]> Date: Mon Apr 3 09:51:46 2017 +0000 Add 'rm -f .testrepository/times.dbm' command in testenv Running py2* post py3* tests results in error. Add 'rm -f .testrepository/times.dbm' command in testenv to resolve this. Change-Id: I17f872b6169317de7c541a2ed77344ab1c313f94 Closes-Bug: #1229445 ** Changed in: magnum Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1229445 Title: db type could not be determined Status in Ironic: Fix Released Status in Magnum: Fix Released Status in OpenStack Compute (nova): Fix Released Status in Testrepository: Triaged Bug description: In openstack/python-novaclient project, run test in py27 env, then run test in py33 env, the following error will stop test: db type could not be determined But, if you run "tox -e py33" fist, then run "tox -e py27", it will be fine, no error. workaround: remove the file in .testrepository/times.dbm, then run py33 test, it will be fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ironic/+bug/1229445/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
