cover: another 'db type could not be determined' workaround 83/38483/1
authorRoss Brattain <ross.b.brattain@intel.com>
Mon, 31 Jul 2017 21:13:58 +0000 (14:13 -0700)
committerRoss Brattain <ross.b.brattain@intel.com>
Mon, 31 Jul 2017 21:14:21 +0000 (14:14 -0700)
Change-Id: Ib94ff2dfc86725e5367908296b5160f9565442b8
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
tests/ci/cover.sh

index 0c7c235..6e4d608 100644 (file)
@@ -47,6 +47,9 @@ run_coverage_test() {
 
     # Generate and save coverage report
     current_report=$(mktemp -t yardstick_coverageXXXXXXX)
+    # workaround 'db type could not be determined' bug
+    # https://bugs.launchpad.net/testrepository/+bug/1229445
+    rm -f .testrepository/times.dbm
     find . -type f -name "*.pyc" -delete && python setup.py testr --coverage --testr-args="$*"
     coverage report > $current_report
     current_missing=$(awk 'END { print $3 }' $current_report)