[
https://issues.apache.org/jira/browse/STORM-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14222513#comment-14222513
]
ASF GitHub Bot commented on STORM-492:
--------------------------------------
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/316#issuecomment-64136784
@harshach Yes, you're right. I didn't intend it.
Btw, how about using higher value between system environment and each unit
test's custom timeout?
@javrasha I thought you saw STORM-492 carefully, but you didn't.
To achieve setting up each test's timeout, it shouldn't rely on system
property, it should be done with wait-until-cluster-waiting's parameter, and
pick higher value.
> Test timeout should be configurable
> -----------------------------------
>
> Key: STORM-492
> URL: https://issues.apache.org/jira/browse/STORM-492
> Project: Apache Storm
> Issue Type: Bug
> Reporter: Devika Nair
> Assignee: Jungtaek Lim
> Labels: newbie
> Fix For: 0.9.3-rc2
>
>
> Test timeout is hard coded to 5000ms in
> https://github.com/apache/incubator-storm/blob/master/storm-core/src/clj/backtype/storm/testing.clj.
> Provide a way to override this value in order to handle longer running tests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
