[
https://issues.apache.org/jira/browse/YETUS-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved YETUS-711.
------------------------------------
Resolution: Not A Bug
Closing this as not a bug as there is no actual Yetus problem here given that
the unit test failure is reproducible outside of Yetus.
> maven unit test result is different when running "mvn test
> -Dtest=TestContainerLaunch" under different directories
> ------------------------------------------------------------------------------------------------------------------
>
> Key: YETUS-711
> URL: https://issues.apache.org/jira/browse/YETUS-711
> Project: Yetus
> Issue Type: Bug
> Reporter: Zhankun Tang
> Priority: Major
>
> Found this issue when YARN-7277 (on trunk). The patches consist of changesÂ
> under both "hadoop-yarn-api" and "hadoop-yarn-server-nodemanager". In
> essence, the code changes are doing some string replacement. For instance, a
> constructed string
> "{{HADOOP_COMMON_HOME}}" will be transformed to "$HADOOP_COMMON_HOME". After
> the patch, the constructed string will be "{_{HADOOP_COMMON_HOME}_}" and
> still expected to be transformed to "$HADOOP_COMMON_HOME".
> The fact is that, when doing unit test, Yetus runs "mvn test
> -Dtest=TestContainerLaunch" under "hadoop-yarn-server-nodemanager" and failed
> with a weird output.
> I can reproduce the same error output with "mvn clean package -DskipTests
> -DskipShade" and "cd hadoop-yarn-server-nodemanager" and then "mvn test
> -Dtest=TestContainerLaunch".
> But when I run above mvn test command in parent direcotry "hadoop-yarn" or
> "hadoop-yarn-project", the unit test will success.
> I think the above issue is quite strange. So please help on this.
> And another thing weirder is that when I run "mvn clean test
> -DTestContainerLaunch" under nodemanager direcotry, the error output is
> different with Yetus error output.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
