[
https://issues.apache.org/jira/browse/HADOOP-14368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15992859#comment-15992859
]
Steve Loughran commented on HADOOP-14368:
-----------------------------------------
OK, patch submitted; search for text "ExitException" in string consts also
caught where gridmix would want it as the exclusive text.
FWIW, looking in the tests for all use of ExitException, there's enough of them
it's worth having a variant of {{LambdaTestUtils.intercept()}} which explicitly
looks for exit exceptions of a given status code...if it returns the stdout on
the operation then it could be used for the postprocessing
{code}
String out = interceptExitException(-1, () -> Namenode.main(new
Array<String>[]{"-format3"})
assertContains("unknown", out);
{code}
This'd get rid of a lot of duplication in tests. Of course, that'd need
somebody to go though all the old tests, but we can at least use it for new
Java 8 lang tests...
> ExitUtil change by YARN-679 breaks HDFS tests
> ---------------------------------------------
>
> Key: HADOOP-14368
> URL: https://issues.apache.org/jira/browse/HADOOP-14368
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Kihwal Lee
> Assignee: Steve Loughran
> Priority: Critical
> Attachments: HADOOP-14368-001.patch
>
>
> The following two are broken after YARN-679.
> {noformat}
> TestStartup
> TestMetadataVersionOutput
> {noformat}
> Since it was changing multiple components in common, it should have run hdfs
> tests as well before committing.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
