[
https://issues.apache.org/jira/browse/BEAM-6630?focusedWorklogId=199138&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-199138
]
ASF GitHub Bot logged work on BEAM-6630:
----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Feb/19 09:42
Start Date: 15/Feb/19 09:42
Worklog Time Spent: 10m
Work Description: adude3141 commented on issue #7787: [BEAM-6630] upgrade
to gradle 5.2
URL: https://github.com/apache/beam/pull/7787#issuecomment-463972152
Hmm... nice.
Unfortunately, I have now idea how this is (or even could be) related to the
gradle upgrade. We probably reduced memory available to the test jvm (was:
1/4th of physically available mem, is: 2G). I assume, we do have more than 8G
on the Jenkins agents, but I did not find yet any documentation on that.
Even if mem would be increased now - and test jvm was gc'ing all the time, I
have no idea, why batch should require significantly more memory compared to
streaming?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 199138)
Time Spent: 1h 50m (was: 1h 40m)
> Upgrade Gradle to 5.2
> ---------------------
>
> Key: BEAM-6630
> URL: https://issues.apache.org/jira/browse/BEAM-6630
> Project: Beam
> Issue Type: Improvement
> Components: build-system
> Reporter: Michael Luckey
> Assignee: Michael Luckey
> Priority: Minor
> Fix For: 2.11.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> - Reenables build cache with jacoco
> - java 11 support (see https://issues.apache.org/jira/browse/BEAM-2530)
> - some improvements in build time expected
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
