[
https://issues.apache.org/jira/browse/HDFS-13819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16578669#comment-16578669
]
Daniel Templeton commented on HDFS-13819:
-----------------------------------------
We're not seeing the failure in the upstream test runs. It's only appearing
for us on our internal tests, and only rarely. But it is the same test code as
upstream:
{quote}java.lang.AssertionError: expected:<2> but was:<1>
at
org.apache.hadoop.hdfs.server.datanode.TestDirectoryScanner.verifyStats(TestDirectoryScanner.java:337)
at
org.apache.hadoop.hdfs.server.datanode.TestDirectoryScanner.testDirectoryScannerInFederatedCluster(TestDirectoryScanner.java:1074){quote}
I wasn't able to reproduce a failure in 500 runs on my laptop. This is the
problem with these integration tests pretending to be unit tests. They're
inherently flaky, but it takes the right environment.
I'll let it sit for another day and then commit.
> TestDirectoryScanner#testDirectoryScannerInFederatedCluster is flaky
> --------------------------------------------------------------------
>
> Key: HDFS-13819
> URL: https://issues.apache.org/jira/browse/HDFS-13819
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
> Affects Versions: 3.0.0
> Reporter: Daniel Templeton
> Assignee: Daniel Templeton
> Priority: Minor
> Attachments: HDFS-13819.001.patch, HDFS-13819.002.patch
>
>
> We're seeing the test fail periodically with:
> {quote}java.lang.AssertionError: expected:<2> but was:<1>{quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
