[ZEPPELIN-665] travis CI change to not rerun interpreter tests #708
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.
What is this PR for?
While investigating CI failure with PR #706, I noticed that we were running all tests in each of 6 jobs in the test matrix.
It seems we have accidentally switched back to running all tests even with older versions of Spark. (from PR #626
Filtering out interpreter tests for these runs help make test jobs faster (~30%) and also reduce the chance that an interpreter test might intermittently fail, thus hopefully improve CI reliability.
Also changing Spark 1.2.1 to 1.2.2 (last 1.2.x release)
What type of PR is it?
Improvement
Todos
Is there a relevant Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-665
How should this be tested?
Run Travis CI
Screenshots (if appropriate)
N/A
Questions: