[
https://issues.apache.org/jira/browse/YETUS-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673089#comment-16673089
]
Allen Wittenauer commented on YETUS-711:
----------------------------------------
bq. 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.
But that's not what it's doing. Looking at the top of the log file, it's
specifically running
{code}
/usr/bin/mvn --batch-mode
-Dmaven.repo.local=/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/yetus-m2/hadoop-trunk-patch-1
-Ptest-patch -Pparallel-tests -P!shelltest -Pnative -Drequire.fuse
-Drequire.openssl -Drequire.snappy -Drequire.valgrind -Drequire.test.libhadoop
-Pyarn-ui clean test -fae
{code}
which means that another test could be conflicting with TestContainerLaunch.
What happens when you run the full test?
bq. 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.
If that's the actual command line that you ran, then you did run the full test
suite. It threw an error which means something really is broken in YARN.
It doesn't sound like there is a Yetus bug here.
> 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)
