beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henning Rohde (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-3057) Jenkins test run sometimes fail with "ERROR: Maven JVM terminated unexpectedly with exit code 137"
Date Wed, 03 Jan 2018 18:07:00 GMT

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

Henning Rohde commented on BEAM-3057:
-------------------------------------

This continues to happen:

https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Apex/3119/console


> Jenkins test run sometimes fail with "ERROR: Maven JVM terminated unexpectedly with exit
code 137"
> --------------------------------------------------------------------------------------------------
>
>                 Key: BEAM-3057
>                 URL: https://issues.apache.org/jira/browse/BEAM-3057
>             Project: Beam
>          Issue Type: Bug
>          Components: testing
>            Reporter: Valentyn Tymofieiev
>            Assignee: Jason Kuster
>
> Example failed runs:
> https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15049/console
> https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15053/console
> https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/15042/console
> The first two runs have other test errors, the third run does not seem to contain test
errors.  
> https://stackoverflow.com/questions/24989653/jenkins-maven-build-137-error/24991433 suggests
increasing the memory available to JVM might help.
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message