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....@web.de>
---
t/perf/p0004-lazy-init-name-hash.sh | 4 ----
1 file changed, 4 deletions(-)
diff --git a/t/perf/p0004-lazy-init-name-hash.sh
b/t/perf/p0004-lazy-init-name-hash.sh
index d30c32f97b..3c2135a185 100755
--- 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) &&
--
2.12.2
