From 826f27b101086ea220689a1691ef6553b5c72a4e Mon Sep 17 00:00:00 2001
From: Jeff Bezanson <jeff.bezanson@gmail.com>
Date: Wed, 10 Aug 2016 17:39:13 -0400
Subject: [PATCH] fix BigInt `ndigits` test

See #16766. `ndigits(big(0),1)` doesn't raise an error, but we were
sometimes (randomly, rarely) testing that it does. This change makes
the test reliable. The issue of how this case should actually
behave is still open.

(cherry picked from commit dd09d19f6545a87cef384378d6956ce48c04d9a5)
ref #17952
---
 test/bigint.jl | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/test/bigint.jl b/test/bigint.jl
index 999b0c42cf6dd..0478b28f8b286 100644
--- a/test/bigint.jl
+++ b/test/bigint.jl
@@ -278,7 +278,11 @@ ndigits_mismatch(n) = ndigits(n) != ndigits(BigInt(n))
 ndigits(rand(big(-999:999)), rand(63:typemax(Int)))
 ndigits(rand(big(-999:999)), big(2)^rand(2:999))
 
-@test_throws DomainError ndigits(rand(big(-999:999)), rand(typemin(Int):1))
+for i in big([-20:-1;1:20])
+    for b in -10:1
+        @test_throws DomainError ndigits(i, b)
+    end
+end
 
 # conversion from float
 @test BigInt(2.0) == BigInt(2.0f0) == BigInt(big(2.0)) == 2