Hadoop QA commented on YARN-2689:

{color:green}+1 overall{color}.  Here are the results of testing the latest 
  against trunk revision cdce883.

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

    {color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified test files.

    {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/5391//console

This message is automatically generated.

> TestSecureRMRegistryOperations failing on windows
> -------------------------------------------------
>                 Key: YARN-2689
>                 URL: https://issues.apache.org/jira/browse/YARN-2689
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api, resourcemanager
>    Affects Versions: 2.6.0
>         Environment: Windows server, Java 7, ZK 3.4.6
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>         Attachments: YARN-2689-001.patch
> the micro ZK service used in the {{TestSecureRMRegistryOperations}} test 
> doesnt start on windows, 
> {code}
> org.apache.hadoop.service.ServiceStateException: java.io.IOException: Could 
> not configure server because SASL configuration did not allow the  ZooKeeper 
> server to authenticate itself properly: 
> javax.security.auth.login.LoginException: Unable to obtain password from user
> {code}

This message was sent by Atlassian JIRA

Reply via email to