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

Sean Busbey commented on HBASE-20314:
-------------------------------------

this feels like hitting a resource limit, e.g. # threads, or the like. I see 
we're up on Yetus 0.7.0 now for precommit, but I don't see it reporting how 
close to the limit we are. I don't have time to look at specifics yet, but 
figuring out why we're not reporting that would be my first guess.

or the machine stats on disk space. they're in the build artifacts under 
patchprocess/machine

> Pre commit build for master branch fails
> ----------------------------------------
>
>                 Key: HBASE-20314
>                 URL: https://issues.apache.org/jira/browse/HBASE-20314
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Duo Zhang
>            Priority: Major
>         Attachments: HBASE-20314.patch
>
>
> See here
> https://builds.apache.org/job/PreCommit-HBASE-Build/12208/artifact/patchprocess/patch-unit-hbase-client.txt
> All the surefire tests are failed with
> {noformat}
> [ERROR] Please refer to /testptch/hbase/hbase-client/target/surefire-reports 
> for the individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] ExecutionException The forked VM terminated without properly saying 
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /testptch/hbase/hbase-client && 
> /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -enableassertions 
> -Dhbase.build.id=2018-03-29T14:24:09Z -Xmx2800m 
> -Djava.security.egd=file:/dev/./urandom -Djava.net.preferIPv4Stack=true 
> -Djava.awt.headless=true -jar 
> /testptch/hbase/hbase-client/target/surefire/surefirebooter6093376455951697188.jar
>  /testptch/hbase/hbase-client/target/surefire 2018-03-29T14-24-22_719-jvmRun1 
> surefire3061343808153644548tmp surefire_07554325011124878578tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] ExecutionException The forked VM terminated without properly saying 
> goodbye. VM crash or System.exit called?
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to