[
https://issues.apache.org/jira/browse/HDFS-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15062569#comment-15062569
]
Hudson commented on HDFS-9565:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #8985 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/8985/])
HDFS-9565. (arp: rev 72a3f649e4db2b1cc18a8e203c321cc1832435e4)
*
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestDistributedFileSystem.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
> TestDistributedFileSystem.testLocatedFileStatusStorageIdsTypes is flaky due
> to race condition
> ---------------------------------------------------------------------------------------------
>
> Key: HDFS-9565
> URL: https://issues.apache.org/jira/browse/HDFS-9565
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: fs, test
> Affects Versions: 3.0.0
> Environment: Jenkins
> Reporter: Wei-Chiu Chuang
> Assignee: Wei-Chiu Chuang
> Priority: Minor
> Fix For: 2.8.0
>
> Attachments: HDFS-9565.001.patch
>
>
> TestDistributedFileSystem.testLocatedFileStatusStorageIdsTypes occasionally
> fails with the following error:
> https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/699/testReport/org.apache.hadoop.hdfs/TestDistributedFileSystem/testLocatedFileStatusStorageIdsTypes/
> {noformat}
> FAILED:
> org.apache.hadoop.hdfs.TestDistributedFileSystem.testLocatedFileStatusStorageIdsTypes
> Error Message:
> Unexpected num storage ids expected:<2> but was:<1>
> Stack Trace:
> java.lang.AssertionError: Unexpected num storage ids expected:<2> but was:<1>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at
> org.apache.hadoop.hdfs.TestDistributedFileSystem.testLocatedFileStatusStorageIdsTypes(TestDistributedFileSystem.java:855)
> {noformat}
> It appears that this test failed due to race condition: it does not wait for
> the file replication to finish, before checking the file's status.
> This flaky test can be fixed by using DFSTestUtil.waitForReplication()
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
