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
Modeling locks as synchronization points causes blind spots, but this was likely a design decision made to ensure high performance and no false positives
As a result, adding property-based race detection, specifically for finding mutex lock race conditions, would be quite useful to add to rapid.
In an Erlang quickcheck paper there are details on how they are able to use parallel property-based testing to find race conditions, and it would be nice if these mechanisms were supported by Rapid.