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
Leaking goroutines is a problem that's hard to spot. We can help users detect these goroutines by adding a -leak flag to go test that detects leaking goroutines. A rough outline of the lifecycle of a test in the presence of this flag is as follows:
Count non-test, non-runtime goroutines
Run the test
Wait some period of time for things to shut down (possibly configurable with a default of 100ms, for instance)
Count non-test, non-runtime goroutines
If before != after, err
The text was updated successfully, but these errors were encountered:
Inspired by grpc-go's leak detector (example usage here) by @menghanl and co.
Leaking goroutines is a problem that's hard to spot. We can help users detect these goroutines by adding a
-leak
flag togo test
that detects leaking goroutines. A rough outline of the lifecycle of a test in the presence of this flag is as follows:The text was updated successfully, but these errors were encountered: