[
https://issues.apache.org/jira/browse/HADOOP-9624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xi Fang updated HADOOP-9624:
----------------------------
Summary: TestFSMainOperationsLocalFileSystem failed when the Hadoop
enlistment root path has "x" or "X" in its name (was:
TestFSMainOperationsLocalFileSystem and
TestNativeAzureFileSystemOperationsMocked failed when the Hadoop enlistment
root path has "x" or "X" in its name)
> TestFSMainOperationsLocalFileSystem failed when the Hadoop enlistment root
> path has "x" or "X" in its name
> ----------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-9624
> URL: https://issues.apache.org/jira/browse/HADOOP-9624
> Project: Hadoop Common
> Issue Type: Test
> Components: test
> Affects Versions: 1-win
> Environment: Windows
> Reporter: Xi Fang
> Priority: Minor
> Labels: test
>
> TestFSMainOperationsLocalFileSystem and
> TestNativeAzureFileSystemOperationsMocked failed when the Hadoop enlistment
> root path has "x" or "X" in its name. Here is the the root cause of the
> failures.
> Both classes extend Class FSMainOperationsBaseTest. PathFilter
> FSMainOperationsBaseTest#TEST_X_FILTER checks if a path has "x" or "X" in its
> name. Some of the test cases construct a path by combining path
> "TEST_ROOT_DIR" with a customized partial path.
> The problem is that once the enlistment root path has "x" or "X" in its
> name, "TEST_ROOT_DIR" will also has "x" or "X" in its name. The path check
> will pass even if the customized partial path doesn't have "x" or "X".
> However, the path filter is supposed to reject this path when the customized
> partial path doesn't have "x" or "X".
> An easy fix is using more complicated char sequence rather than a simple char
> "x" or "X".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
