[
https://issues.apache.org/jira/browse/HADOOP-13818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15676534#comment-15676534
]
Steve Loughran commented on HADOOP-13818:
-----------------------------------------
That means the time is coming back as " 15/11/2016, 02:15:44 GMT+0:00", not the
value set.
# we could improve the assertions for more details there (which field is
playing up, what the time in human values is)
# we could consider whether atime is going to be settable on all filesystems,
and then how to react to it. Downgrade to warn?
HADOOP-12045 looks at this issue. Maybe macos is getting things wrong. Which FS
is this? The classic HFS+ or the fancy new one?
> TestLocalFileSystem#testSetTimes fails
> --------------------------------------
>
> Key: HADOOP-13818
> URL: https://issues.apache.org/jira/browse/HADOOP-13818
> Project: Hadoop Common
> Issue Type: Bug
> Components: test
> Reporter: Akira Ajisaka
> Priority: Minor
>
> {noformat}
> Running org.apache.hadoop.fs.TestLocalFileSystem
> Tests run: 20, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 4.887 sec
> <<< FAILURE! - in org.apache.hadoop.fs.TestLocalFileSystem
> testSetTimes(org.apache.hadoop.fs.TestLocalFileSystem) Time elapsed: 0.084
> sec <<< FAILURE!
> java.lang.AssertionError: expected:<23456000> but was:<1479176144000>
> 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.junit.Assert.assertEquals(Assert.java:542)
> at
> org.apache.hadoop.fs.TestLocalFileSystem.checkTimesStatus(TestLocalFileSystem.java:391)
> at
> org.apache.hadoop.fs.TestLocalFileSystem.testSetTimes(TestLocalFileSystem.java:414)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
