Hadoop QA commented on YARN-2549:

{color:red}-1 overall{color}.  Here are the results of testing the latest 
  against trunk revision 54e5794.

    {color:green}+1 @author{color}.  The patch does not contain any @author 

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
                        Also please list what manual steps were performed to 
verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with 

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4940//console

This message is automatically generated.

> TestContainerLaunch fails due to classpath problem with hamcrest classes.
> -------------------------------------------------------------------------
>                 Key: YARN-2549
>                 URL: https://issues.apache.org/jira/browse/YARN-2549
>             Project: Hadoop YARN
>          Issue Type: Test
>          Components: nodemanager, test
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>            Priority: Minor
>         Attachments: YARN-2549.1.patch
> The mockito jar bundles its own copy of the hamcrest classes, and it's ahead 
> of our hamcrest dependency jar on the test classpath for 
> hadoop-yarn-server-nodemanager.  Unfortunately, the version bundled in 
> mockito doesn't match the version we need, so it's missing the 
> {{CoreMatchers#containsString}} method.  This causes the tests to fail with 
> {{NoSuchMethodError}} on Windows.

This message was sent by Atlassian JIRA

Reply via email to