[
https://issues.apache.org/jira/browse/LANG-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15071668#comment-15071668
]
Charles Honton commented on LANG-1194:
--------------------------------------
Dumping the memory usage using the MemoryMXBean:
heap init:493,929,088 commited:2,930,245,632 max:7,025,983,488
used:2,307,514,072
non-heap init:24,576,000 commited:25,034,752 max:224,395,264 used:17,364,104
The committed heap memory is close to 3G limit. Travis 3G limit is probably
total footprint. We'll need to allow for the maven footprint and jvm non-heap
memory.
> Travis-ci build fails occasionally with "Killed" message
> --------------------------------------------------------
>
> Key: LANG-1194
> URL: https://issues.apache.org/jira/browse/LANG-1194
> Project: Commons Lang
> Issue Type: Bug
> Components: lang.*
> Affects Versions: 3.4
> Reporter: Charles Honton
> Assignee: Charles Honton
>
> travis-ci build occasionally fails with a "Killed" message in the log.
> The killed test is usually one of:
> org.apache.commons.lang3.StringEscapeUtilsTest
> org.apache.commons.lang3.HashSetvBitSetTest
> org.apache.commons.lang3.builder.ToStringStyleConcurrencyTest
> org.apache.commons.lang3.time.FastDateFormat_ParserTest
> If travis build is restarted, the build will eventually pass.
> The build with same code in other environments does not occur on any local
> environment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
