mirror of https://github.com/hashicorp/consul
Browse Source
If there is imperfect goroutine lifespan tracking if we pipe our logs through testing.T.Logf there is a chance of a stray goroutine attempting to log after the test that spawned it completes. This results in a panic of: panic: Log in goroutine after TestLeader_SecondaryCA_Initialize has completed... This isn't great and should be fixed, but quickly runs into situations around externally cancelling blocking queries which isn't terribly possible at the moment. The concession here is to ignore these specific panics for now. This can be triggered easily when running some tests with a high `-count=YYY` value.pull/6644/head
R.B. Boyer
5 years ago
committed by
GitHub
1 changed files with 13 additions and 0 deletions
Loading…
Reference in new issue