Travis-CI #48
Merged
Travis-CI #48
Conversation
This file contains hidden or 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
- Resolves #37 - Test using MPICH on Ubuntu and Mac OS X - Builds in under 2 minutes after caching MPICH on ubuntu - Builds under 2 minutes with precompiled binaries on OS X
zbeekman
added a commit
that referenced
this pull request
May 31, 2016
zbeekman
added a commit
that referenced
this pull request
Jun 4, 2016
zbeekman
added a commit
that referenced
this pull request
Jun 4, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Pull request to enable Travis-CI continuous integration testing on the master branch.
I'm intentionally doing this before attempting to reconcile some issues I discussed with @rouson about master and branch-1.0.0 being out of sync, so that I/we have the added assurance of the CI tests when I start to tackle that.
Also, I disabled the
coarray_navier_stokestest but ONLY when running under Travis-CI since it is producing an error that can't be produced elsewhere.If anyone can determine the source of that issue, seen here we can certainly turn this test back on for Travis.