Hadoop QA commented on YARN-2343:

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

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

This message is automatically generated.

> Improve error message on token expire exception
> -----------------------------------------------
>                 Key: YARN-2343
>                 URL: https://issues.apache.org/jira/browse/YARN-2343
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Li Lu
>            Assignee: Li Lu
>            Priority: Trivial
>              Labels: usability
>         Attachments: YARN-2343-072314.patch
> Some of token expire exception is triggered by wrong time settings on cluster 
> nodes, but the current exception message does not explicitly address that. It 
> would be helpful to add some message explicitly pointing out that this 
> exception could be caused by machines out of sync in time, or even wrong time 
> zone settings. 

This message was sent by Atlassian JIRA

Reply via email to