increase community build timeouts #161
Merged
Conversation
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
when the Scala version bumps, it's now become routine for the build to hit the old 600 minute limit and time out. we have continued to gradually add projects (and additional resolvers), and existing projects can be expected to gradually add dependencies and grow their test suites and so forth, so I'm not too alarmed about it. in practice, the usual way of coping with this is to fix the Scala SHA whenever manually triggering test runs, so that the whole thing doesn't have to be redone from scratch. admittedly, the build is still slower than we would like! the ticket on that is scala/community-build#152
SethTisue
added a commit
that referenced
this pull request
Jan 29, 2016
…ut-again increase community build timeouts
|
deployed, also. |
|
fwiw, last increase was #129 |
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.
when the Scala version bumps, it's now become routine for the build to
hit the old 600 minute limit and time out.
we have continued to gradually add projects (and additional
resolvers), and existing projects can be expected to gradually add
dependencies and grow their test suites and so forth, so I'm not too
alarmed about it.
in practice, the usual way of coping with this is to fix the Scala
SHA whenever manually triggering test runs, so that the whole thing
doesn't have to be redone from scratch.
admittedly, the build is still slower than we would like! the ticket
on that is scala/community-build#152