-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Deadlocks inside Akka.Remote.TestKit #1134
Comments
Another set of logs from earlier today: http://petabridge-ci.cloudapp.net/viewLog.html?buildId=1524&buildTypeId=AkkaNet_AkkaNetPrBuild&tab=buildLog&guest=1
|
Resolved by #1777 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The multi-node testkit is essential for the Akka.NET v1.1 release, and we've only just recently started running it on 100% of nightly and PR builds.
There appears to be a deadlock condition that occurs when a transition inside the
TestPlayer
orConductor
fails; see this build log from a recent deadlock:http://petabridge-ci.cloudapp.net/viewLog.html?buildId=1514&buildTypeId=AkkaNet_AkkaNetPrBuild&tab=buildLog&guest=1
The text was updated successfully, but these errors were encountered: