summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRené Scharfe <l.s.r@web.de>2017-05-13 18:03:22 +0200
committerJunio C Hamano <gitster@pobox.com>2017-05-16 11:11:52 +0900
commit7b0d409eb28c4c92fa292dfc3ac468cb0f42d2bf (patch)
treea773eba91219fc6d66c2b573b1d0774b077d6322
parent48a6ace8f5a504cea47d4058744982f2bfb81f2f (diff)
downloadgit-7b0d409eb28c4c92fa292dfc3ac468cb0f42d2bf.tar.gz
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>
-rwxr-xr-xt/perf/p0004-lazy-init-name-hash.sh4
1 files changed, 0 insertions, 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) &&