[ 
https://issues.apache.org/jira/browse/HDFS-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026559#comment-14026559
 ] 

Hudson commented on HDFS-6257:
------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk #1797 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1797/])
HDFS-6257. TestCacheDirectives#testExceedsCapacity fails occasionally (cmccabe) 
(cmccabe: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1601473)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestCacheDirectives.java


> TestCacheDirectives#testExceedsCapacity fails occasionally
> ----------------------------------------------------------
>
>                 Key: HDFS-6257
>                 URL: https://issues.apache.org/jira/browse/HDFS-6257
>             Project: Hadoop HDFS
>          Issue Type: Test
>          Components: caching
>    Affects Versions: 2.4.0
>            Reporter: Ted Yu
>            Assignee: Colin Patrick McCabe
>            Priority: Minor
>             Fix For: 2.5.0
>
>         Attachments: HDFS-6257.001.patch
>
>
> From https://builds.apache.org/job/Hadoop-Hdfs-trunk/1736/ :
> REGRESSION:  
> org.apache.hadoop.hdfs.server.namenode.TestCacheDirectives.testExceedsCapacity
> {code}
> Error Message:
> Namenode should not send extra CACHE commands expected:<0> but was:<2>
> Stack Trace:
> java.lang.AssertionError: Namenode should not send extra CACHE commands 
> expected:<0> but was:<2>
>         at org.junit.Assert.fail(Assert.java:93)
>         at org.junit.Assert.failNotEquals(Assert.java:647)
>         at org.junit.Assert.assertEquals(Assert.java:128)
>         at org.junit.Assert.assertEquals(Assert.java:472)
>         at 
> org.apache.hadoop.hdfs.server.namenode.TestCacheDirectives.testExceedsCapacity(TestCacheDirectives.java:1419)
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to