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

Steve Loughran updated HADOOP-14553:
------------------------------------
    Attachment: HADOOP-14553-005.patch

Patch 005

Move a lot more to the parallel phase of the tests. Some of these are 
explicitly using root relative paths, as they need it (no parent directory 
probes/connect). This will work provided all the tests are set up to use names 
guaranteed to be unique across all test suites/methods.

Testing: each moved test worked well alone; a full bulk test failed (lots of 
timeouts), when run over slow network.& 8 parallel tests

I think I'll bump up the default timeout from 30s to something bigger, even 
though its a sign that there's not enough B/W for 8 tests together. Making the 
timeout 600s would be less brittle over slow connections.



> Add (parallelized) integration tests to hadoop-azure
> ----------------------------------------------------
>
>                 Key: HADOOP-14553
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14553
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/azure
>    Affects Versions: 2.9.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>         Attachments: HADOOP-14553-001.patch, HADOOP-14553-002.patch, 
> HADOOP-14553-003.patch, HADOOP-14553-004.patch, HADOOP-14553-005.patch
>
>
> The Azure tests are slow to run as they are serialized, as they are all 
> called Test* there's no clear differentiation from unit tests which Jenkins 
> can run, and integration tests which it can't.
> Move the azure tests {{Test*}} to integration tests {{ITest*}}, parallelize 
> (which includes having separate paths for every test suite). The code in 
> hadoop-aws's POM &c show what to do.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to