[
https://issues.apache.org/jira/browse/HADOOP-13614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15537463#comment-15537463
]
Chris Nauroth commented on HADOOP-13614:
----------------------------------------
I haven't reviewed the entire patch yet, but I am consistently seeing test
timeout failures from {{ITestS3ADeleteManyFiles}} and
{{ITestS3ADeleteFilesOneByOne}} after applying it. The timeout value changed
significantly with this patch.
Old timeout inherited from {{S3AScaleTestBase}}:
{code}
@Rule
public Timeout testTimeout = new Timeout(30 * 60 * 1000);
{code}
New timeout inherited from {{AbstractFSContractTestBase}}:
{code}
public static final int DEFAULT_TEST_TIMEOUT = 180 * 1000;
{code}
These tests consistently take longer than 3 minutes for me to run, testing
against US-west-2. I think these tests will need to override
{{AbstractFSContractTestBase#getTestTimeoutMillis()}} to restore the old
timeout value.
> Purge some superfluous/obsolete S3 FS tests that are slowing test runs down
> ---------------------------------------------------------------------------
>
> Key: HADOOP-13614
> URL: https://issues.apache.org/jira/browse/HADOOP-13614
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3, test
> Affects Versions: 2.9.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Attachments: HADOOP-13614-branch-2-001.patch,
> HADOOP-13614-branch-2-002.patch, HADOOP-13614-branch-2-002.patch, testrun.txt
>
>
> Some of the slow test cases contain tests that are now obsoleted by newer
> ones. For example, {{ITestS3ADeleteManyFiles}} has the test case
> {{testOpenCreate()}} which writes then reads files up 25 MB.
> Have a look at which of the s3a tests are taking time, review them to see if
> newer tests have superceded the slow ones; and cut them where appropriate.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
