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
{{ message }}
This repository has been archived by the owner on May 18, 2023. It is now read-only.
When running tests in my application with -race, they fail due to a race accessing m.now outside of a lock. To my knowledge there are two reads (runNextTimer(...) and Timer(...)) and the write is within runNextTimer. This was hit in my application when calling mock.After(...) from multiple goroutines.
Hello,
When running tests in my application with
-race
, they fail due to a race accessingm.now
outside of a lock. To my knowledge there are two reads (runNextTimer(...)
andTimer(...)
) and the write is withinrunNextTimer
. This was hit in my application when callingmock.After(...)
from multiple goroutines.Example output from an example test I wrote that demonstrates this:
The text was updated successfully, but these errors were encountered: