You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2016/06/01 21:41:59 UTC

[jira] [Commented] (HADOOP-13231) Isolate test path used by a few S3A tests for more reliable parallel execution.

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

Chris Nauroth commented on HADOOP-13231:
----------------------------------------

{{TestS3A}} uses a path of /tests3afc, without consideration of the fork ID in parallel mode.

{{TestS3ADeleteManyFiles#testOpenCreate}} uses a path of /tests3a, also without consideration of the parallel fork ID.

I don't believe there is any reason these tests need to run in isolation during the sequential phase.  We can make the paths include the fork ID. 

> Isolate test path used by a few S3A tests for more reliable parallel execution.
> -------------------------------------------------------------------------------
>
>                 Key: HADOOP-13231
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13231
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3, test
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>            Priority: Minor
>
> I have noticed a few more spots in S3A tests that do not make use of the isolated test directory path when running in parallel mode.  While I don't have any evidence that this is really causing problems for parallel test runs right now, it would still be good practice to clean these up.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org