[
https://issues.apache.org/jira/browse/HADOOP-16971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17086046#comment-17086046
]
Ayush Saxena commented on HADOOP-16971:
---------------------------------------
Got a bit confused from the description.
Can you help with the steps to repro this, as in what sequence to run the
tests, so as to lead to the failure
> testFileContextResolveAfs creates dangling link and fails for subsequent runs
> -----------------------------------------------------------------------------
>
> Key: HADOOP-16971
> URL: https://issues.apache.org/jira/browse/HADOOP-16971
> Project: Hadoop Common
> Issue Type: Bug
> Components: common, fs, test
> Affects Versions: 3.2.1, 3.4.0
> Reporter: Ctest
> Priority: Minor
> Labels: easyfix, fs, symlink, test
> Attachments: HADOOP-16971.000.patch
>
>
> In the test testFileContextResolveAfs, the symlink TestFileContextResolveAfs2
> (linked to TestFileContextResolveAfs1) cannot be deleted when the test
> finishes.
> This is because TestFileContextResolveAfs1 was always deleted before
> TestFileContextResolveAfs2 when they were both passed into
> FileSystem#deleteOnExit. This caused TestFileContextResolveAfs2 to become a
> dangling link, which FileSystem in Hadoop currently cannot delete. (This is
> because Files#exists will return false for dangling links.)
> As a result, the test `testFileContextResolveAfs` only passed for the first
> run. And for later runs of this test, it will fail by throwing the following
> exception:
> {code:java}
> fs.FileUtil (FileUtil.java:symLink(821)) - Command 'ln -s
> mypath/TestFileContextResolveAfs1 mypath/TestFileContextResolveAfs2' failed 1
> with: ln: mypath/TestFileContextResolveAfs2: File exists
> java.io.IOException: Error 1 creating symlink
> file:mypath/TestFileContextResolveAfs2 to mypath/TestFileContextResolveAfs1
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
