[
https://issues.apache.org/jira/browse/HADOOP-10072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805707#comment-13805707
]
Hadoop QA commented on HADOOP-10072:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12610384/HADOOP-10072.1.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}. The javadoc tool did not generate any
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-nfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3250//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3250//console
This message is automatically generated.
> TestNfsExports#testMultiMatchers fails due to non-deterministic timing around
> cache expiry check.
> -------------------------------------------------------------------------------------------------
>
> Key: HADOOP-10072
> URL: https://issues.apache.org/jira/browse/HADOOP-10072
> Project: Hadoop Common
> Issue Type: Bug
> Components: nfs, test
> Affects Versions: 3.0.0, 2.2.0
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Priority: Trivial
> Attachments: HADOOP-10072.1.patch
>
>
> {{TestNfsExports#testMultiMatchers}} has been failing sporadically in my
> environment. The final step of this test is to check that a cache entry has
> expired. It looks like the timing is too tight around this check.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
