[ 
https://issues.apache.org/jira/browse/HADOOP-13113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris Nauroth updated HADOOP-13113:
-----------------------------------
    Attachment: HADOOP-13113.003.patch

I'm attaching patch v003.  This adds the rety loop on 
{{TestS3AContractRootDir#testListEmptyRootDirectory}}.  I also took the 
opportunity to clear some Checkstyle nits in files I'm touching.

bq. Do we need to rely on a new system property, or could we just rely on the 
test class name being unique? that is {{this.getClass().getName()}} could 
provide the path?

Currently the patch relies on overriding 
{{AbstractBondedFSContract#getTestPath}} as a convenient place to parameterize 
the test path per unique fork.  This layer of the code doesn't have direct 
access to the test suite class.  We could change the contract classes so that 
the test suite class needs to be passed in during construction, but then every 
test suite would need to be changed.  Overall, I prefer what the current patch 
is doing, but I could be convinced otherwise if you feel strongly about it.


> Enable parallel test execution for hadoop-aws.
> ----------------------------------------------
>
>                 Key: HADOOP-13113
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13113
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: test
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>         Attachments: HADOOP-13113.001.patch, HADOOP-13113.002.patch, 
> HADOOP-13113.003.patch
>
>
> The full hadoop-aws test suite takes ~30 minutes to execute.  The tests spend 
> most of their time blocked on network I/O with the S3 back-end, but they 
> don't saturate the bandwidth of the NIC.  We can improve overall execution 
> time by enabling parallel test execution.



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

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

Reply via email to