[
https://issues.apache.org/jira/browse/HDFS-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272064#comment-14272064
]
Hadoop QA commented on HDFS-7598:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12691381/HDFS-7598.001.patch
against trunk revision ae91b13.
{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 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
hadoop-hdfs-project/hadoop-hdfs-nfs.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/9173//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/9173//console
This message is automatically generated.
> TestDFSClientCache.testEviction is not quite correct and fails with newer
> version of guava
> ------------------------------------------------------------------------------------------
>
> Key: HDFS-7598
> URL: https://issues.apache.org/jira/browse/HDFS-7598
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Affects Versions: 2.6.0
> Reporter: Sangjin Lee
> Assignee: Sangjin Lee
> Priority: Minor
> Attachments: HDFS-7598.001.patch
>
>
> TestDFSClientCache.testEviction() is not entirely accurate in its usage of
> the guava LoadingCache.
> It sets the max size at 2, but asserts the loading cache will contain only 1
> entry after inserting two entries. Guava's CacheBuilder.maximumSize() makes
> only the following promise:
> {panel}
> Specifies the maximum number of entries the cache may contain. Note that the
> cache may evict an entry before this limit is exceeded.
> {panel}
> Thus, the only invariant is that the loading cache will hold the maximum size
> number of entries or fewer. The DFSClientCache.testEviction asserts it holds
> maximum size - 1 exactly.
> For guava 11.0.2 this happens to be true at maximum size = 2 because of the
> way it sets the maximum segment weight. With later versions of guava, the
> maximum segment weight is set higher, and the eviction is less aggressive.
> The test should be fixed to assert only the true invariant.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
