[
https://issues.apache.org/jira/browse/HDFS-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16490964#comment-16490964
]
Íñigo Goiri commented on HDFS-13620:
------------------------------------
This doesn't really fix the Windows related issue.
This just makes sure that a failed unit test doesn't take down the full test
class.
I would make the current [^HDFS-13620.000.patch] a separate JIRA as it applies
in general.
For the Windows issue itself, I've seen this issue too.
The problem is that the first test (it follows alphabetical order so it's
testAppend) takes a long time to start.
We should figure out why poll0 takes so long the first time.
> TestHDFSFileSystemContract fails on Windows
> -------------------------------------------
>
> Key: HDFS-13620
> URL: https://issues.apache.org/jira/browse/HDFS-13620
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Anbang Hu
> Assignee: Anbang Hu
> Priority: Minor
> Labels: Windows
> Attachments: HDFS-13620-branch-2.000.patch, HDFS-13620.000.patch
>
>
> According to [hadoop-win-trunk #476
> TestHDFSFileSystemContract|https://builds.apache.org/job/hadoop-trunk-win/476/testReport/org.apache.hadoop.hdfs/TestHDFSFileSystemContract/],
> TestHDFSFileSystemContract fails on Windows starting from
> TestHDFSFileSystemContract #testAppend timeout, locking directory path for
> MiniDFSCluster for the following tests.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
