Split build tasks on travis fixes #1242#1256
Merged
Merged
Conversation
I believe the frequent scalajs build failure is caused by out of memory, So splitting the tasks helped. This is verified by #1254 which passes two builds consecutively.
Current coverage is 90.13% (diff: 100%)@@ master #1256 diff @@
==========================================
Files 243 243
Lines 3285 3285
Methods 3231 3231
Messages 0 0
Branches 51 51
==========================================
Hits 2961 2961
Misses 324 324
Partials 0 0
|
This was referenced Aug 2, 2016
Contributor
|
👍 LGTM. It will be so nice to have builds working reliably again. |
Contributor
|
👍 (and fingers crossed that the successes you've seen so far aren't just a fluke). |
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
4 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.
I believe the frequent scalajs build failure is caused by out of memory, So splitting the tasks helped. This is verified by #1254 which passes two builds consecutively.
Update: thanks to @mikejcurry in his comment here I understand we are at the upper bound of memory available on travis, i.e. we can't increase jvm memory to solve this problem.