Add automated testing with circle-ci#55
Merged
jwise77 merged 10 commits intoenzo-project:masterfrom Apr 29, 2019
Merged
Conversation
brittonsmith
commented
Apr 9, 2019
gregbryan
approved these changes
Apr 9, 2019
This was referenced Apr 9, 2019
Merged
jwise77
approved these changes
Apr 11, 2019
Contributor
Author
|
@jwise77, @gregbryan, want to go ahead and merge this in ? |
Contributor
I was waiting on a third review. But I think this is an important addition before moving forward, so I'm merging now. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This adds automated testing using the circle-ci service. The testing is the same push suite as before with an added test of building the docs as well. We now cache external dependencies, like hypre, and the answers from the gold standard. The latter cuts the test time in half.
I had to disable some of the mercurial version checking in the test runner to get things working. I can eventually replace this with the git counterpart, but I think that can wait until after this is accept. None of that affects the running of the tests.