[
https://issues.apache.org/jira/browse/STORM-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14222489#comment-14222489
]
ASF GitHub Bot commented on STORM-492:
--------------------------------------
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/316#issuecomment-64132928
@javrasya @HeartSaVioR I don't understand this change. We already
discussed this in another JIRA that having systemProperty doesn't pass in the
variable to testing.clj. I tested this PR with following command
"mvn clean install -DstormTestTimeoutMs=20000"
and my test timeout still 5000.
If the intention of this patch is for other tests to increase the timeout
they can pass it as parameter to
(defn wait-until-cluster-waiting
"Wait until the cluster is idle. Should be used with time simulation."
([cluster-map] (wait-until-cluster-waiting cluster-map TEST-TIMEOUT-MS))
([cluster-map timeout-ms]
> 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)
