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 "Hudson (Jira)" <ji...@apache.org> on 2019/12/13 16:44:00 UTC
[jira] [Commented] (HADOOP-16757) Increase timeout unit test rule
for MetadataStoreTestBase
[ https://issues.apache.org/jira/browse/HADOOP-16757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995756#comment-16995756 ]
Hudson commented on HADOOP-16757:
---------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #17759 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/17759/])
HADOOP-16757. Increase timeout unit test rule for MetadataStoreTestBase (github: rev d12ad9e8adbce5ee4c9a5883f25c1635cd122878)
* (edit) hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/test/HadoopTestBase.java
* (edit) hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/s3guard/MetadataStoreTestBase.java
> Increase timeout unit test rule for MetadataStoreTestBase
> ---------------------------------------------------------
>
> Key: HADOOP-16757
> URL: https://issues.apache.org/jira/browse/HADOOP-16757
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Mingliang Liu
> Assignee: Mingliang Liu
> Priority: Major
>
> Not sure if this is a good proposal, but I saw a few cases where some integration test methods in {{ITestDynamoDBMetadataStore}} timed out simply. Specially, the one keeps failing me today is {{testAncestorOverwriteConflict}}. I increase the timeout to 200s and it works for me happily. Am I using VPN and a slow home network, I'm afraid so.
> The time out rule, as inherited from base class {{HadoopTestBase}}, is 100s by default. Though that 100s time out default value can be overridden in base class via system property {{test.default.timeout}}, that's system wide affecting all other tests. Changing that time out value for one test is no better than overriding in this test {{ITestDynamoDBMetadataStore}} explicitly. I think doubling it to 200s would not be very crazy considering we are testing against a remote web service, create and destroy tables sometimes.
> Thoughts?
> [EDIT]: I meant 100s when I said 10s. Sorry for confusion.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org