[
https://issues.apache.org/jira/browse/HBASE-12285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14189537#comment-14189537
]
Dima Spivak commented on HBASE-12285:
-------------------------------------
In first run (after addendum) with 2.18-SNAPSHOT, we get
{code}
Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.18-SNAPSHOT:test
(secondPartTestsExecution) on project hbase-server: ExecutionException:
java.lang.RuntimeException: The forked VM terminated without properly saying
goodbye. VM crash or System.exit called?
[ERROR] Command was /bin/sh -c cd
/home/jenkins/jenkins-slave/workspace/HBase-1.0/hbase-server &&
/home/jenkins/tools/java/jdk1.7.0_25-32/jre/bin/java -enableassertions
-XX:MaxDirectMemorySize=1G -Xmx1900m -XX:MaxPermSize=256m
-Djava.security.egd=file:/dev/./urandom -Djava.net.preferIPv4Stack=true
-Djava.awt.headless=true -jar
/home/jenkins/jenkins-slave/workspace/HBase-1.0/hbase-server/target/surefire/surefirebooter8771725147211915636.jar
/home/jenkins/jenkins-slave/workspace/HBase-1.0/hbase-server/target/surefire/surefire4600209770137145770tmp
/home/jenkins/jenkins-slave/workspace/HBase-1.0/hbase-server/target/surefire/surefire_7296048355863863584558tmp
{code}
Let's let it run a handful more times and then reevaluate what's going on here.
> Builds are failing, possibly because of SUREFIRE-1091
> -----------------------------------------------------
>
> Key: HBASE-12285
> URL: https://issues.apache.org/jira/browse/HBASE-12285
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Dima Spivak
> Assignee: Dima Spivak
> Priority: Blocker
> Attachments: HBASE-12285_branch-1_v1.patch,
> HBASE-12285_branch-1_v1.patch
>
>
> Our branch-1 builds on builds.apache.org have been failing in recent days
> after we switched over to an official version of Surefire a few days back
> (HBASE-4955). The version we're using, 2.17, is hit by a bug
> ([SUREFIRE-1091|https://jira.codehaus.org/browse/SUREFIRE-1091]) that results
> in an IOException, which looks like what we're seeing on Jenkins.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
