[ 
https://issues.apache.org/jira/browse/HADOOP-16166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16791942#comment-16791942
 ] 

Hudson commented on HADOOP-16166:
---------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #16200 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/16200/])
HADOOP-16166. TestRawLocalFileSystemContract fails with build Docker 
(matthew_foley: rev f74159c8fc5e7fd0c4357d6dc95ce05f94e60145)
* (edit) 
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/fs/TestRawLocalFileSystemContract.java


> TestRawLocalFileSystemContract fails with build Docker container running on 
> Mac
> -------------------------------------------------------------------------------
>
>                 Key: HADOOP-16166
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16166
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 3.3.0
>            Reporter: Matt Foley
>            Assignee: Matt Foley
>            Priority: Minor
>
> The Mac has a case-insensitive filesystem.  When using the recommended build 
> Docker container via `start-build-env.sh`, the container attaches to the Mac 
> FS to share the local git repository for Hadoop.  Which is very nice and 
> convenient.
> This means the TestRawLocalFileSystemContract#testFilesystemIsCaseSensitive() 
> test case (which is inherited from FileSystemContractBaseTest) should be 
> skipped.  It fails to be skipped, and therefore throws a Unit Test failure, 
> because @Override TestRawLocalFileSystemContract#filesystemIsCaseSensitive() 
> does not take into account the possibility of a Linux OS mounting a MacOS 
> filesystem.
> The fix would extend 
> TestRawLocalFileSystemContract#filesystemIsCaseSensitive() to recognize this 
> case.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to