You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Udi Meiri <eh...@google.com> on 2017/12/20 22:50:35 UTC

"Maven JVM terminated unexpectedly with exit code 137"

I did a quick search about this error and one of the suggestions
<https://stackoverflow.com/questions/24989653/jenkins-maven-build-137-error>
was
that this might an OOM failure (ref:
https://issues.jenkins-ci.org/browse/JENKINS-12035).
Is there a way to get the output of dmesg or similar on the machines
running Jenkins?

This was the failed build:
https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/16333/

Re: "Maven JVM terminated unexpectedly with exit code 137"

Posted by Valentyn Tymofieiev <va...@google.com>.
I believe committers only have access to Jenkins workspaces, so you can try
to open a ticket with INFRA and ask them to ssh and run particular commands
on Jenkins machine.

Related: https://issues.apache.org/jira/browse/BEAM-3057

On Wed, Dec 20, 2017 at 2:50 PM, Udi Meiri <eh...@google.com> wrote:

> I did a quick search about this error and one of the suggestions
> <https://stackoverflow.com/questions/24989653/jenkins-maven-build-137-error> was
> that this might an OOM failure (ref: https://issues.jenkins-ci.org/
> browse/JENKINS-12035).
> Is there a way to get the output of dmesg or similar on the machines
> running Jenkins?
>
> This was the failed build: https://builds.apache.o
> rg/job/beam_PreCommit_Java_MavenInstall/16333/
>
>