[
https://issues.apache.org/jira/browse/HDFS-6104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira AJISAKA resolved HDFS-6104.
---------------------------------
Resolution: Invalid
Assignee: (was: Mit Desai)
Closing this issue because the test was removed by HDFS-6102.
> TestFsLimits#testDefaultMaxComponentLength Fails on branch-2
> ------------------------------------------------------------
>
> Key: HDFS-6104
> URL: https://issues.apache.org/jira/browse/HDFS-6104
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Mit Desai
> Labels: java7
>
> testDefaultMaxComponentLength fails intermittently with the following error
> {noformat}
> java.lang.AssertionError: expected:<0> but was:<255>
> 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.junit.Assert.assertEquals(Assert.java:456)
> at
> org.apache.hadoop.hdfs.server.namenode.TestFsLimits.testDefaultMaxComponentLength(TestFsLimits.java:90)
> {noformat}
> On doing some research, I found that this is actually a JDK7 issue.
> The test always fails when it runs after any test that runs
> addChildWithName() method
--
This message was sent by Atlassian JIRA
(v6.2#6252)