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

Add timeout to Google Test discovery #406

Merged

Conversation

mwoehlke-kitware
Copy link
Member

Tweak Google Test discovery to abort if the test executable fails to complete within 30 seconds. This is a work-around for the thread_pool test which is currently hanging on our Windows dashboard build for reasons not-yet-known. (Curiously, it only hangs when given --gtest_list_tests; when the tests actually run, they pass, and the executable exits normally.)

This is not currently upstream, but I intend to submit a version of this for inclusion in CMake 3.10.1.

Tweak Google Test discovery to abort if the test executable fails to
complete within 30 seconds. This is a work-around for the thread_pool
test which is currently hanging on our Windows dashboard build for
reasons not-yet-known. (Curiously, it only hangs when given
--gtest_list_tests; when the tests actually run, they pass, and the
executable exits normally.)

This is not currently upstream, but I intend to submit a version of this
for inclusion in CMake 3.10.1.
@linus-sherrill linus-sherrill merged commit ffad81b into Kitware:master Nov 27, 2017
@kwcvrobot
Copy link
Collaborator

Linux build succeeded: https://open.cdash.org/buildSummary.php?buildid=5158335

@kwcvrobot
Copy link
Collaborator

Windows build failure: https://open.cdash.org/buildSummary.php?buildid=5158235

@mwoehlke-kitware
Copy link
Member Author

(Note: This feature has been proposed for upstream inclusion as !1534.)

@mwoehlke-kitware mwoehlke-kitware deleted the dev/gtest-discovery-timeout branch November 28, 2017 16:18
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

Successfully merging this pull request may close these issues.

None yet

3 participants