[
https://issues.apache.org/jira/browse/HDFS-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442470#comment-13442470
]
Kihwal Lee commented on HDFS-3856:
----------------------------------
I've run into this problem before where a test is exiting prematurely, causing
surefire to report a fork failure. This is not really the failure of fork()
system call. We get this when a forked test process exits before the test
harness has a chance to do it. For example, the following will generate a fork
failure.
{code}
@Test
public void TestBlowUp() throws InterruptedException {
Thread.sleep(3000);
System.exit(-1);
}
{code}
If the exit code is set to zero in the above example, surefile will still error
out, but it won't be a fork failure. On a related note, I have recently seen
the MiniDFSCluster reporting an exit exception in multiple test cases.
> fork failure running hdfs unit tests trunk and branch-2
> -------------------------------------------------------
>
> Key: HDFS-3856
> URL: https://issues.apache.org/jira/browse/HDFS-3856
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Affects Versions: 3.0.0, 2.2.0-alpha
> Reporter: Thomas Graves
> Priority: Blocker
>
> We have been seeing the hdfs tests on trunk and branch-2 error out with fork
> failures. I see the hadoop jenkins trunk build is also seeing these:
> https://builds.apache.org/view/Hadoop/job/Hadoop-trunk/lastCompletedBuild/console
--
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
