Skip to content
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

Flaky spec: ShouldConnectAndDisconnect (TurboMqtt.Tests.End2End.TcpMqtt311End2EndSpecs) #99

Open
Aaronontheweb opened this issue May 1, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Aaronontheweb
Copy link
Member

ShouldConnectAndDisconnect (TurboMqtt.Tests.End2End.TcpMqtt311End2EndSpecs) failed
/github/workspace/tests/TurboMqtt.Tests/TestResults/_fv-az735-963_2024-05-01_19_40_10.trx [took 0s]

Expected client.IsConnected to be false, but found True.   at FluentAssertions.Execution.XUnit2TestFramework.Throw(String message)
   at FluentAssertions.Execution.TestFrameworkProvider.Throw(String message)
   at FluentAssertions.Execution.DefaultAssertionStrategy.HandleFailure(String message)
   at FluentAssertions.Execution.AssertionScope.FailWith(Func`1 failReasonFunc)
   at FluentAssertions.Primitives.BooleanAssertions`1.BeFalse(String because, Object[] becauseArgs)
   at TurboMqtt.Tests.End2End.TransportSpecBase.ShouldConnectAndDisconnect() in /home/runner/work/TurboMqtt/TurboMqtt/tests/TurboMqtt.Tests/End2End/TransportSpecBase.cs:line 51
--- End of stack trace from previous location ---

I have been able to produce this locally using "Run until Failure" in Rider

@Aaronontheweb Aaronontheweb added the bug Something isn't working label May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant