Test `TestNameserverHasChallenge` sometimes results in an invalid memory address.
Test TestNameserverHasChallenge
sometimes (less than 1% of all test runs) results in an invalid memory address.
=== RUN TestNameserverHasChallenge
--- FAIL: TestNameserverHasChallenge (2.00s)
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x8fd334]
goroutine 66 [running]:
testing.tRunner.func1.2({0x948920, 0xcaf3e0})
/usr/local/go/src/testing/testing.go:1396 +0x372
testing.tRunner.func1()
/usr/local/go/src/testing/testing.go:1399 +0x5f0
panic({0x948920, 0xcaf3e0})
/usr/local/go/src/runtime/panic.go:890 +0x262
git.scc.kit.edu/KIT-CA/acme4netvs/v2.NameserverHasChallenge({0x9b3da7, 0xf}, {0x9b9491, 0x1a}, {0x9af2b9, 0x3})
/home/sprawl/git/KIT-CA/acme4netvs/dns_utils.go:61 +0x394
git.scc.kit.edu/KIT-CA/acme4netvs/v2.TestNameserverHasChallenge(0x0?)
/home/sprawl/git/KIT-CA/acme4netvs/dns_utils_test.go:57 +0x225
testing.tRunner(0xc000206680, 0x9e57c0)
/usr/local/go/src/testing/testing.go:1446 +0x217
created by testing.(*T).Run
/usr/local/go/src/testing/testing.go:1493 +0x75e
exit status 2
FAIL git.scc.kit.edu/KIT-CA/acme4netvs/v2 2.679s