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.
If there are no other builds (for other PRs, branches, ...), switching the JVM/JS order to JS/JVM can be 10-15 minutes quicker.
There are now 6 Travis jobs for every build (3 Scala versions and JVM / JS) and only 5 are executing at the same time. By switching the order, the three longer JVM jobs are started first and when the 2.11 JS job finishes, the 2.12 JS job can start (which doesn't take as long as the 2.12 JVM job which is now started last).
I ran Travis twice resulting in total build times of 31 and 39 minutes while the last master builds took around 50 minutes.
This is just a minor improvement of the Travis matrix build change by @kailuowang in #1671.