You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I got the following error when running my tests with -race enabled.
=== RUN TestUpdateShardKeyRange
race: limit on 8128 simultaneously alive goroutines is exceeded, dying
When race detector crashed with more than 8128 simultaneously alive goroutines, I'd expect the runtime to print out the stacktrace of all those goroutines so I can check whether those goroutines actually suppose to be there.
What did you see instead?
Silent crash without any further info on those excessive number of goroutines.
The text was updated successfully, but these errors were encountered:
Yes, that would be nice to have.
Fortunately, we should be getting a new race detector for 1.19 that doesn't have this limit. See #49761.
So I'm going to close this issue as unnecessary. It will be so nice to be in a world where that error just doesn't happen.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Run my tests with -race enabled.
What did you expect to see?
I got the following error when running my tests with -race enabled.
When race detector crashed with more than 8128 simultaneously alive goroutines, I'd expect the runtime to print out the stacktrace of all those goroutines so I can check whether those goroutines actually suppose to be there.
What did you see instead?
Silent crash without any further info on those excessive number of goroutines.
The text was updated successfully, but these errors were encountered: