From 39b39b0e006831fb18d5acac1c4f07efc39ebdf1 Mon Sep 17 00:00:00 2001
From: Vishvananda Ishaya <vishvananda@gmail.com>
Date: Wed, 20 Feb 2013 19:05:44 -0800
Subject: [PATCH] Use a fake coverage module instead of real one.

Actually loading the coverage module was leading to odd concurrency
conditions where it was interfering with mocked calls. This changes
to stub out the coverage class with a fake one so that we don't have
to worry about collisions. It also modifies the coverage class to be
created lazily so it isn't automatically started at import time.
Finally it removes the hack in run_tests.sh ignoring the coverage
tests.

Fixes bug 1131023

Change-Id: I39de434454f8b0903f6311e731e215a93027bc91
---
 run_tests.sh | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/run_tests.sh b/run_tests.sh
index 9872858b4..68a564754 100755
--- a/run_tests.sh
+++ b/run_tests.sh
@@ -110,10 +110,6 @@ function run_tests {
   ${wrapper} find . -type f -name "*.pyc" -delete
 
   if [ $coverage -eq 1 ]; then
-    # Do not test test_coverage_ext when gathering coverage.
-    if [ "x$testrargs" = "x" ]; then
-      testrargs="^(?!.*test.*coverage).*$"
-    fi
     TESTRTESTS="$TESTRTESTS --coverage"
   else
     TESTRTESTS="$TESTRTESTS --slowest"