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

Some tests intermittently fail to terminate on OSX #194

Closed
jen20 opened this issue Aug 20, 2014 · 6 comments
Closed

Some tests intermittently fail to terminate on OSX #194

jen20 opened this issue Aug 20, 2014 · 6 comments
Assignees

Comments

@jen20
Copy link
Contributor

jen20 commented Aug 20, 2014

When running ./run_tests.sh on Mac OS X, some tests (currently not sure which) intermittently do not terminate, instead enqueuing messages such as this ad infinitum:

[00828,15,23:14:40.447,DEBUG] EventStoreConnection 'ESC-109': enqueueing message EventStore.ClientAPI.Core.HandleTcpPackageMessage..
[00828,15,23:14:40.447,DEBUG] EventStoreConnection 'ESC-109': HandleTcpPackage connId 96996068-9a59-4527-8673-38adde53d497, package HeartbeatResponseCommand, 3389a251-8a60-4b6a-a163-c5f3f1e0e64a..
@jen20 jen20 added this to the v3.0.0 milestone Aug 20, 2014
@jen20 jen20 self-assigned this Aug 20, 2014
@gregoryyoung
Copy link
Contributor

That is just heartbeat messages over the connection that is still alive.

On Tue, Aug 19, 2014 at 8:56 PM, James Nugent notifications@github.com
wrote:

When running ./run_tests.sh on Mac OS X, some tests (currently not sure
which) intermittently do not terminate, instead enqueuing messages such as
this ad infinitum:

[00828,15,23:14:40.447,DEBUG] EventStoreConnection 'ESC-109': enqueueing message EventStore.ClientAPI.Core.HandleTcpPackageMessage..
[00828,15,23:14:40.447,DEBUG] EventStoreConnection 'ESC-109': HandleTcpPackage connId 96996068-9a59-4527-8673-38adde53d497, package HeartbeatResponseCommand, 3389a251-8a60-4b6a-a163-c5f3f1e0e64a..


Reply to this email directly or view it on GitHub
#194.

Studying for the Turing test

@jen20
Copy link
Contributor Author

jen20 commented Aug 20, 2014

Yes, the question is what is stopping it closing in the first place. I suspect it's a similar issue that we've seen before (on Linux) where the timeout on a close doesn't actually work.

@jen20
Copy link
Contributor Author

jen20 commented Sep 10, 2014

This is highly intermittent. I can't figure out what is going on - sometimes the full suite will pass, sometimes a single test will fail. My guess is that a wait handle isn't being hit so MiniNodes aren't being torn down correctly.

@jen20 jen20 modified the milestones: v4.0.0, v3.0.0 Sep 17, 2014
@jen20
Copy link
Contributor Author

jen20 commented Sep 17, 2014

Pushing this to v4.0.0. I have no idea wtf nunit is doing underneath on OS X.

@gregoryyoung
Copy link
Contributor

Any update on this? Have you run nunit with trace so you can see which tests are the ones causing the issue?

@pgermishuys
Copy link
Contributor

I haven't seen this on any of the officially supported platforms. Have seen flapping tests which are handled on a case by case basis, but since OSX isn't a supported platform, is this still relevant?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants