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
TcpConnectionSpec.An_Outgoing_Connection_Must_Send_Only_One_ClosedEvent_To_The_Handler_If_The_Handler_Commanded_The_Close intermittent test failure
#1170
Open
Aaronontheweb opened this issue
Jul 18, 2015
· 2 comments
Saw an intermittent failure on TcpConnectionSpec.An_Outgoing_Connection_Must_Send_Only_One_ClosedEvent_To_The_Handler_If_The_Handler_Commanded_The_Close in #1169.
I will spin up a couple of instances on AWS to try and reproduce this more reliably. Should I create PR to skip TcpConnectionSpec temporarily while I look into this?
@willieferguson I think it'd be useful not to skip it for now - see how often it actually comes up in subsequent PRs built on the CI servers. Plus it's also possible that @rogeralsing's PR #1169 didn't have your latest racy spec fix pulled into it, which might explain this.
The CI server build agents run on Azure Standard M4 instances with 2 cores and 8 GB of RAM. They're designed to be semi-lightweight machines as they help expose racy / soft real-time issues more often than our personal development machines do.
Saw an intermittent failure on
TcpConnectionSpec.An_Outgoing_Connection_Must_Send_Only_One_ClosedEvent_To_The_Handler_If_The_Handler_Commanded_The_Close
in #1169.Full build log is available here http://petabridge-ci.cloudapp.net/viewLog.html?buildId=1696&buildTypeId=AkkaNet_AkkaNetPrBuild&guest=1
The text was updated successfully, but these errors were encountered: