Only run 2 tasks at once during Travis JS build #1808
Merged
Conversation
This file contains 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
|
Coverage remained the same at 17.964% when pulling af9e4651cebdaa40bc74793eb1ebd8f791def630 on update/travis-parallel-commands into 8284fa6 on master. |
nylen
force-pushed
the
update/travis-parallel-commands
branch
from
af9e465
to
9d11d47
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Recent Travis build times look highly variable:
The change in pattern here coincides with switching to Jest in #1382.
After adding coverage reporting in #1783, we are putting even more stress on the Travis CI container that runs the JavaScript CI job. It's effectively running 4 jobs at once:
npm run buildnpm run lint(Jest will use 2 workers because our Travis containers have 2 cores and Jest defaults to 1 worker per core.)
This PR changes the CI job to run only two concurrent tasks:
npm run lint, thennpm run buildI'll run a few builds against this PR and use the same
travis-statsapp to verify that build times are shorter and/or more consistent.