Output after every Wycheproof primality test.
Running that many primality tests, particularly on large numbers, in a
single test case is slow and timing out Chromium's test runner.
Change-Id: I07363744970545b2b4fcd7be264e20c338765dea
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/39564
Reviewed-by: Adam Langley <agl@google.com>
diff --git a/crypto/fipsmodule/bn/bn_test.cc b/crypto/fipsmodule/bn/bn_test.cc
index e5f03a8..18a7edc 100644
--- a/crypto/fipsmodule/bn/bn_test.cc
+++ b/crypto/fipsmodule/bn/bn_test.cc
@@ -2343,7 +2343,14 @@
/*do_trial_division=*/true, nullptr));
EXPECT_EQ(result.IsValid() ? 1 : 0, is_probably_prime);
}
+ // Running many large primality tests in a single test case is slow,
+ // so output after test to prevent Chromium from timing out.
+ // Chromium's test infrastructure assume that a test binary not
+ // producing output for too long is hanging.
+ putchar('.');
+ fflush(stdout);
});
+ putchar('\n');
}
TEST_F(BNTest, NumBitsWord) {
