GEODE-5615: Removing gradle build scan plugin #2365
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
Based on heap dumps from a gradle daemon that was close to running out of memory, all of it's memory is full of build scan related objects, including what looks like all of the test standard out.
Contributor
Author
|
@rhoughton-pivot @smgoller |
Contributor
|
Well that’s not a very good design. Yes pull it! |
jake-at-work
approved these changes
Aug 22, 2018
Contributor
|
Nice! |
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.
The build scan plugin appears to be buffering all test output in memory, causing
the gradle daemon to run out of memory for DistributedTest. We're not even using
the build scan plugin by default. Removing this fixed the OOMEs.