[
https://issues.apache.org/jira/browse/HDFS-3582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410122#comment-13410122
]
Aaron T. Myers commented on HDFS-3582:
--------------------------------------
bq. I wouldn't justify this fix purely for testing, though HADOOP-8096 shows
utility at run time.
Why not? We sometimes have tests that fail that we can't adequately debug
because of this. That seems like reason enough to me that we should address
this issue.
bq. It is not the Hadoop team's fault that Surefire can't handle process exit
calls, especially given that Apache Ant has happily done so for twelve years.
Certainly not our fault, but we still suffer the consequences. Since we have a
(pretty simple) way to work around the limitation, I think we should implement
it.
> Hook daemon process exit for testing
> -------------------------------------
>
> Key: HDFS-3582
> URL: https://issues.apache.org/jira/browse/HDFS-3582
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: test
> Affects Versions: 2.0.0-alpha
> Reporter: Eli Collins
> Assignee: Eli Collins
> Priority: Minor
> Attachments: hdfs-3582.txt, hdfs-3582.txt, hdfs-3582.txt,
> hdfs-3582.txt, hdfs-3582.txt
>
>
> Occasionally the tests fail with "java.util.concurrent.ExecutionException:
> org.apache.maven.surefire.booter.SurefireBooterForkException:
> Error occurred in starting fork, check output in log" because the NN is
> exit'ing (via System#exit or Runtime#exit). Unfortunately Surefire doesn't
> retain the log output (see SUREFIRE-871) so the test log is empty, we don't
> know which part of the test triggered which exit in HDFS. To make this easier
> to debug let's hook all daemon process exits when running the tests.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
