-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deadlock detected by TestConnReaperDeadlock #149
Comments
Seems that Then next call to |
Synthetic test hard to make but its enough to have two clients dialed to server and then close those clients. Not even needs 5/10 as in TestConnReaperDeadlock. Then you need to make either multiple runs or artificial delays to ensure sequence in prev message. |
Fixes #149 Co-authored-by: Sergey Egorov <sergey.egorov@teleste.com> Co-authored-by: Sebastien Binet <binet@cern.ch>
Running
while go test -timeout 30s -run ^TestConnReaperDeadlock$; do echo .; done
with v0.16.0 eventually may get test failed by timeoutThe output is next:
go-zeromq/zmq4 v0.16.0
go version 1.21.5
The text was updated successfully, but these errors were encountered: