You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Charles Honton (JIRA)" <ji...@apache.org> on 2015/12/25 17:55:49 UTC

[jira] [Commented] (LANG-1194) Travis-ci build fails occasionally with "Killed" message

    [ https://issues.apache.org/jira/browse/LANG-1194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15071666#comment-15071666 ] 

Charles Honton commented on LANG-1194:
--------------------------------------

travis-ci documentation mentions that build will be killed if more than 10 minutes passes between log messages or if total memory of VM exceeds 3G.  Since entire build takes less than 8 minutes, I've investigated the memory concern.

> 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)