-
Notifications
You must be signed in to change notification settings - Fork 45
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
Fix Travis CI build of TriBITS #240
Labels
Comments
bartlettroscoe
added a commit
that referenced
this issue
Nov 10, 2017
bartlettroscoe
added a commit
that referenced
this issue
Nov 10, 2017
bartlettroscoe
added a commit
that referenced
this issue
Nov 10, 2017
bartlettroscoe
added a commit
that referenced
this issue
Nov 10, 2017
The Travis CI build did not have any timeout set for the tests. Therefore, if any one test hung, it would result in a timeout of the overall Travis CI build and no test results would show up on the TriBITS CDash site. This change gives what I think is a pretty reasonble default of 60s.
bartlettroscoe
added a commit
that referenced
this issue
Nov 10, 2017
For some reason, these tests hang on the Travis CI with CMake 3.9.0. Since the tests are timing out, I can't see any output from the test to know where the test is hanging. But these are just four tests that are timing out and I test these locally so it should be okay. Build/Test Cases Summary Enabled Packages: Enabled all Packages 0) MPI_DEBUG => passed: passed=263,notpassed=0 (0.79 min) 1) SERIAL_RELEASE => passed: passed=263,notpassed=0 (0.62 min) 2) MPI_DEBUG_CMAKE-3.6.2 => passed: passed=284,notpassed=0 (0.67 min) 3) SERIAL_RELEASE_CMAKE-3.6.2 => passed: passed=284,notpassed=0 (0.51 min) Other local commits for this build/test group: 47e37cc
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Travis CI build just started failing yesterday. The most recent build shown at:
with CDash output shown at:
shows that the CMake version was upgraded from 3.2.2 to 3.9.2 as shown at:
as compared to an earlier build showing 3.2.3 shown at:
This results in more tests getting run and some of the tests timing out.
The text was updated successfully, but these errors were encountered: