cover.sh: delete .testrepository before running coverage 95/38495/1
authorRoss Brattain <ross.b.brattain@intel.com>
Tue, 1 Aug 2017 02:34:16 +0000 (19:34 -0700)
committerRoss Brattain <ross.b.brattain@intel.com>
Tue, 1 Aug 2017 02:34:16 +0000 (19:34 -0700)
When running py27 and py3 test ran into problems
with .testrepository already exists, but testr
thinking it was corrupt

running testr
No repository found in /home/jenkins/opnfv/slave_root/workspace/yardstick-verify-master. Create one by running "testr init".
error: testr failed (3)

The fix seems to be to delete .testrepository before
running testr coverage

Change-Id: Ib8cd3ab9d3384935380ac29ce365439c6464adc3
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
tests/ci/cover.sh

index 6e4d608..822ed2f 100644 (file)
@@ -36,8 +36,8 @@ run_coverage_test() {
     baseline_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="$*"
+    rm -rf .testrepository
+    find . -type f -name "*.pyc" -delete && python setup.py testr --coverage --slowest --testr-args="$*"
     coverage report > $baseline_report
     baseline_missing=$(awk 'END { print $3 }' $baseline_report)
 
@@ -49,8 +49,8 @@ run_coverage_test() {
     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="$*"
+    rm -rf .testrepository
+    find . -type f -name "*.pyc" -delete && python setup.py testr --coverage --slowest --testr-args="$*"
     coverage report > $current_report
     current_missing=$(awk 'END { print $3 }' $current_report)