-
Notifications
You must be signed in to change notification settings - Fork 6
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
Stomp Tests Timeout Forever #401
Comments
this annoyed me just today. one time too many. will fix |
got some work for this by mistake into #441 |
should we have some |
They should always run in CI, and I haven't seen any problems with them in CI, have you? I see the problem when running locally. We already have a |
nevermind, I missed that mark at first. |
todo: should add here in a new PR changes that were explored in #364 PR |
one possible course of action is to mock - change this in the tests: |
running |
what I see is that the test fails but then the debugger keeps running |
solved with #491 |
If I run the stomp tests without a valid message bus running, they should fail within the 10 second timeout (they usually fail earlier when disconnection occurs). They currently hang forever, this behaviour seems to have been present since #345 so probably has something to do with the fact that we are now logging exceptions rather than raising them. This would be unfortunate as it means our solution that made the CLI easier to use makes the tests harder to use.
This ticket is therefore to come up with a solution to #220 that also works for this.
The text was updated successfully, but these errors were encountered: