[
https://issues.apache.org/jira/browse/HADOOP-10394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925365#comment-13925365
]
Hadoop QA commented on HADOOP-10394:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12633615/HADOOP-10394.02.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 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
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) 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
hadoop-common-project/hadoop-auth.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3650//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3650//console
This message is automatically generated.
> TestAuthenticationFilter is flaky
> ---------------------------------
>
> Key: HADOOP-10394
> URL: https://issues.apache.org/jira/browse/HADOOP-10394
> Project: Hadoop Common
> Issue Type: Bug
> Components: test
> Affects Versions: 2.3.0
> Reporter: Arpit Agarwal
> Assignee: Arpit Agarwal
> Attachments: HADOOP-10394.01.patch, HADOOP-10394.02.patch
>
>
> We have seen this assert cause occasional failures on Ubuntu.
> {code}
> Assert.assertEquals(System.currentTimeMillis() + 1000 * 1000,
> token.getExpires(), 100);
> {code}
> The expected fudge is up to 100ms, we have seen up to ~110ms in practice.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
