Fix unit test valgrind hangs #700
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
codemercenary
added a commit
that referenced
this pull request
Jul 31, 2015
Fix unit test valgrind hangs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Three unit tests were consistently hanging under valgrind, making it impractical to do sanity-checks with valgrind ./AutowiringTest. Until now I had to run select tests or use --gtest_filter with a negative pattern.
How this fixes it: There seems to be no guarantee that a spin-loop thread will ever yield. Adding these WaitForEvent() calls ensure that bolt/transmitter/receiver actually gets a chance to run.