[
https://issues.apache.org/jira/browse/HADOOP-10072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HADOOP-10072:
-----------------------------------
Attachment: HADOOP-10072.1.patch
I'm attaching a patch that changes the assertion to poll every 500 ms for the
expired entry, up to a maximum of 5 seconds. With this patch, the test passes
for me consistently in multiple environments.
This is basically the same logic as {{GenericTestUtils#waitFor}}, but I wanted
to avoid introducing a test dependency from hadoop-nfs to hadoop-common just
for one call to that method.
> 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)
