[
https://issues.apache.org/jira/browse/HDFS-11372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839151#comment-15839151
]
Xiao Chen commented on HDFS-11372:
----------------------------------
Sure Yiqun, will take a look. Thanks.
bq. So in my opition, we just adding the missing timeout for the test method is
enough.
Adding a {{@Rule}} to the test class would be sufficient then.
> Increase test timeouts that are too aggressive.
> -----------------------------------------------
>
> Key: HDFS-11372
> URL: https://issues.apache.org/jira/browse/HDFS-11372
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: test
> Affects Versions: 3.0.0-alpha3
> Reporter: Xiao Chen
> Priority: Minor
>
> Seen these timeout in some
> [precommit|https://issues.apache.org/jira/browse/HDFS-10899?focusedCommentId=15838964&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15838964]
> false positives, at a brief look I think likely due to timeout being to
> small.
> - TestLeaseRecovery2
> - TestDataNodeVolumeFailure
> Can't seem to find from jenkins which test method is at fault, but
> TestLeaseRecovery2 has some 30-second timeout cases, and
> TestDataNodeVolumeFailure has 1 10-second timeout case.
> We should make them at least 2 minutes, or maybe 10x local run time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
