p0004: don't abort if multi-threaded is too slow

If the single-threaded variant beats the multi-threaded one then we may
have a performance bug, but that doesn't justify aborting the test.
Drop that check; we can compare the results for --single and --multi
using the actual performance tests.

Signed-off-by: Rene Scharfe <l.s.r@web.de>
Acked-by: Jeff Hostetler <git@jeffhostetler.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>

diff --git a/t/perf/p0004-lazy-init-name-hash.sh b/t/perf/p0004-lazy-init-name-hash.sh
index d30c32f97b3bdbe1464e307e8bea26adb4a5c2cc..3c2135a18527b75e7cae69b827b6732a792fe7cd 100755 (executable)
--- a/t/perf/p0004-lazy-init-name-hash.sh
+++ b/t/perf/p0004-lazy-init-name-hash.sh
@@ -14,10 +14,6 @@ test_expect_success 'verify both methods build the same hashmaps' '
        test_cmp sorted.single sorted.multi
 '
 
-test_expect_success 'multithreaded should be faster' '
-       test-lazy-init-name-hash --perf >out.perf
-'
-
 test_expect_success 'calibrate' '
        entries=$(wc -l <out.single) &&