[
https://issues.apache.org/jira/browse/HDFS-10934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15537011#comment-15537011
]
Mingliang Liu commented on HDFS-10934:
--------------------------------------
[~ebadger], it's a nice catch! I think the patch will fix this.
I then realized that perhaps I should not rely on the assumption mtime1 ==
mtime2 in the first place. We simple mkdir, create file (and close it), get
file status, get dir status, and do the assertions against respective mtime.
The file status and dir status are free to be different. This way, the test
code is more straightforward and a bit easier to read/maintain. Any thoughts?
Thanks.
> TestDFSShell.testStat fails intermittently
> ------------------------------------------
>
> Key: HDFS-10934
> URL: https://issues.apache.org/jira/browse/HDFS-10934
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Eric Badger
> Assignee: Eric Badger
> Attachments: HDFS-10934.001.patch
>
>
> Saw this failure in an internal build. Reran the test 30 times and it failed
> once with the same type of failure.
> {noformat}
> org.junit.ComparisonFailure: Unexpected -stat output: 2016-09-30 03:48:56
> 2016-09-30 03:48:57
> expected:<...6
> 2016-09-30 03:48:5[7]
> > but was:<...6
> 2016-09-30 03:48:5[6]
> >
> at org.junit.Assert.assertEquals(Assert.java:115)
> at org.apache.hadoop.hdfs.TestDFSShell.testStat(TestDFSShell.java:2082)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
