You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Alan Burlison (JIRA)" <ji...@apache.org> on 2015/11/18 17:05:10 UTC

[jira] [Created] (HADOOP-12583) Sundry symlink problems on Solaris

Alan Burlison created HADOOP-12583:
--------------------------------------

             Summary: Sundry symlink problems on Solaris
                 Key: HADOOP-12583
                 URL: https://issues.apache.org/jira/browse/HADOOP-12583
             Project: Hadoop Common
          Issue Type: Sub-task
          Components: fs
    Affects Versions: 2.7.1
         Environment: Solaris
            Reporter: Alan Burlison
            Priority: Minor


There are various filesystem test failures on Solaris:

{code}
  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>
{code}

I'm not sure what the root cause it, most likely Linux-specific assumptions about how symlinks behave. Further investigation needed.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)