[
https://issues.apache.org/jira/browse/DRILL-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17532734#comment-17532734
]
ASF GitHub Bot commented on DRILL-8172:
---------------------------------------
luocooong commented on code in PR #2500:
URL: https://github.com/apache/drill/pull/2500#discussion_r866652340
##########
.travis.yml:
##########
@@ -45,6 +45,9 @@ cache:
before_install:
- export JAVA_HOME="/usr/lib/jvm/java-8-openjdk-arm64"
- export PATH="$JAVA_HOME/bin:$PATH"
+ - export MEMORYMB=2048
Review Comment:
The GitHub CI uses 7GB and Travis CI uses close to 8GB.
In the GitHub CI, we using the java managed heap is 2500 MB, and java direct
memory is 4500MB, 168MB is reserved for OS. In the Travis CI, we can up the
managed heap to 2500MB, but I also recommend keeping the direct memory at 5GB.
> Use the specified memory usage for Travis CI
> --------------------------------------------
>
> Key: DRILL-8172
> URL: https://issues.apache.org/jira/browse/DRILL-8172
> Project: Apache Drill
> Issue Type: Bug
> Components: Tools, Build & Test
> Reporter: Cong Luo
> Assignee: Cong Luo
> Priority: Major
>
> Unlike GitHub CI, Travis CI may have more memory. If so, we can run unit
> tests using various policies to prevent failure.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
