Travis: Move regression tests to separate build #1030
Merged
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 patch removes the regression test from the standard Travis job and
moves it to a new job. We also run all regression tests before
reporting the status code, and report a fail if any of the test give a
different result. All files which have changed are reported at the end
of the job.
Code coverage tests have also been moved out of the invariance tests and
into the regression testing. They continue to be based on symmetric
grids.
This test also combines the whitespace and documentation auditing into a
a single test, in order to stay within 3 concurrent tests.