Open leighmcculloch opened 2 years ago
One of the lines noted in the output is a call to t.Logf
, so maybe it's a bad idea for us to be calling that function inside the go routine. I was under the impression calls to the t
were behind a mutex, and so safe to do concurrently, but this error suggests not so.
There's a data race in this concurrency test. This was seen in an CI run.