[
https://issues.apache.org/jira/browse/HADOOP-9920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756309#comment-13756309
]
Yu Li commented on HADOOP-9920:
-------------------------------
Hi Jason,
Comparing the error message logged in HADOOP-9853 and here, I don't think they
are completely the same, but since patch attached here will upgrade the
maven-surefire-plugin version to 2.16, I guess the patch might also resolve the
issue mentioned in HADOOP-9853.
I'm sure with patch here, it at least won't hit SUREFIRE-910 any more. :-)
> Should upgrade maven-surefire-plugin version to avoid hitting SUREFIRE-910
> --------------------------------------------------------------------------
>
> Key: HADOOP-9920
> URL: https://issues.apache.org/jira/browse/HADOOP-9920
> Project: Hadoop Common
> Issue Type: Bug
> Components: test
> Affects Versions: 2.1.0-beta
> Reporter: Yu Li
> Assignee: Yu Li
> Attachments: HADOOP-9920.patch
>
>
> While running UT against 2.1.0-beta on our own Jenkins server, the UT was
> interruptted at hadoop common project with below exception:
> {noformat}
> ExecutionException; nested exception is
> java.util.concurrent.ExecutionException: java.lang.RuntimeException: The
> forked VM terminated without saying properly goodbye. VM crash or System.exit
> called ?
> {noformat}
> And further checking proves we have ran into
> [SUREFIRE-910|http://jira.codehaus.org/browse/SUREFIRE-910] which reports the
> same issue which got fixed in surefire v2.13 while our maven-surefire-plugin
> version is still 2.12.3 for now. We should upgrade it to the latest 2.16
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
