Details
-
Sub-task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.7.1
-
None
-
None
-
Solaris
Description
There are various filesystem test failures on Solaris, all related to symlinks:
TestSymlinkLocalFSFileContext>TestSymlinkLocalFS.testDanglingLink:156 expected:<[alanbur]> but was:<[]> TestSymlinkLocalFSFileContext>TestSymlinkLocalFS.testSetTimesSymlinkToDir:233->SymlinkBaseTest.testSetTimesSymlinkToDir:1391 expected:<1447788288000> but was:<3000> TestSymlinkLocalFSFileContext>TestSymlinkLocalFS.testSetTimesSymlinkToFile:227->SymlinkBaseTest.testSetTimesSymlinkToFile:1376 expected:<1447788290000> but was:<3000> TestSymlinkLocalFSFileSystem>TestSymlinkLocalFS.testDanglingLink:156 expected:<[alanbur]> but was:<[]> TestSymlinkLocalFSFileSystem>TestSymlinkLocalFS.testSetTimesSymlinkToDir:233->SymlinkBaseTest.testSetTimesSymlinkToDir:1391 expected:<1447788416000> but was:<3000> TestSymlinkLocalFSFileSystem>TestSymlinkLocalFS.testSetTimesSymlinkToFile:227->SymlinkBaseTest.testSetTimesSymlinkToFile:1376 expected:<1447788417000> but was:<3000>
I'm not sure what the root cause is, most likely Linux-specific assumptions about how symlinks behave. Further investigation needed.
Attachments
Issue Links
- is related to
-
HADOOP-12603 TestSymlinkLocalFSFileContext#testSetTimesSymlinkToDir occasionally fail
- Resolved