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

rscharfe · gitster · commit 7b0d409eb28c · 2017-05-16T11:11:52.000+09:00
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 &lt;l.s.r@web.de&gt;
Acked-by: Jeff Hostetler &lt;git@jeffhostetler.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
diff --git 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) &&
 

Original file line number	Diff line number	Diff line change
`@@ -14,10 +14,6 @@ test_expect_success 'verify both methods build the same hashmaps' '`
`14`	`14`	`test_cmp sorted.single sorted.multi`
`15`	`15`	`'`
`16`	`16`
`17`		`-test_expect_success 'multithreaded should be faster' '`
`18`		`- test-lazy-init-name-hash --perf >out.perf`
`19`		`-'`
`20`		`-`
`21`	`17`	`test_expect_success 'calibrate' '`
`22`	`18`	`entries=$(wc -l <out.single) &&`
`23`	`19`