[
https://issues.apache.org/jira/browse/HADOOP-10072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805997#comment-13805997
]
Hudson commented on HADOOP-10072:
---------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #4659 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/4659/])
HADOOP-10072. TestNfsExports#testMultiMatchers fails due to non-deterministic
timing around cache expiry check. Contributed by Chris Nauroth. (cnauroth:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1535918)
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/trunk/hadoop-common-project/hadoop-nfs/src/test/java/org/apache/hadoop/nfs/TestNfsExports.java
> 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)