hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Klochkov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4491) Parallel testing HDFS
Date Tue, 19 Feb 2013 01:24:11 GMT

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

Andrey Klochkov commented on HDFS-4491:
---------------------------------------

Chris, as far as I can understand "trunk" doesn't support Windows currently. Many tests fail
and it doesn't seem there's an easy way to overcome this. I noticed branch "branch-trunk-win"
which seems to be dedicated to Windows support - is it correct? Unfortunately I couldn't proceed
too far with a Windows VM and using this branch, as one of the requirements is MS Visual Studio
which I don't have. 

Looking at the code in "trunk" I see that there are 14 tests using hardcoded paths of the
form "/tmp/<class name>". I'n not completely clear about the reasons of this, can you
please answer to clarify:
1. Why are these fixes applied to trunk while in general Windows support is kept in "branch-trunk-win"?
2. Why are just a few tests fixed? There are many others which use "test.build.data"
3. Is it a proper way to fix it? There are reasons of using "test.build.data" to place all
test data under. E.g. this data can be placed on ramfs to speedup testing.
                
> Parallel testing HDFS
> ---------------------
>
>                 Key: HDFS-4491
>                 URL: https://issues.apache.org/jira/browse/HDFS-4491
>             Project: Hadoop HDFS
>          Issue Type: Test
>          Components: test
>    Affects Versions: 3.0.0
>            Reporter: Tsuyoshi OZAWA
>            Assignee: Andrey Klochkov
>         Attachments: HDFS-4491.patch
>
>
> Parallel execution of HDFS tests in multiple forks. See HADOOP-9287 for details.

--
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

Mime
View raw message