I've spent quite a bit of time trying to figure out the cause of flaky test runs such as this:

https://ci.appveyor.com/project/rabbitmq/rabbitmq-dotnet-client/builds/42483470

  Failed TestBasicAckAfterChannelRecovery [15 s]
  Error Message:
     waiting on a latch timed out
  Expected: True
  But was:  False

This is the test that is usually flaky:

https://github.com/rabbitmq/rabbitmq-dotnet-client/blob/6.x/projects/Unit/TestConnectionRecovery.cs#L78-L84

TL;DR of what the test does:

• Opens an auto-recovering consuming connection and model
• Opens a publishing connection and model
• Sets up event handlers and reset events for connection shutdown and recovery on the consuming connection/model
• Publishes messages, and mid-publishing uses rabbitmqctl to forcibly close the connection
• Waits for connection recovery
• Ensures the rest of the messages are consumed

Update - this is due to a bug introduced here:

9e4b5ac#diff-8ac157517768ceec4089eb71059693ba4529f49c165989d85327d5c16e317007R146