[
https://issues.apache.org/jira/browse/STORM-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178871#comment-14178871
]
ASF GitHub Bot commented on STORM-492:
--------------------------------------
Github user ptgoetz commented on a diff in the pull request:
https://github.com/apache/storm/pull/279#discussion_r19171864
--- Diff: DEVELOPER.md ---
@@ -229,6 +229,9 @@ The following commands must be run from the top-level
directory.
# Build the code and run the tests (requires nodejs, python and ruby
installed)
$ mvn clean install
+ # Build the code and run the tests, with specifying default test
timeout (in millisecond)
+ $ mvn clean install -DSTORM_TEST_TIMEOUT_MS=10000
--- End diff --
@HeartSaVioR Let's go with an environment variable. In my testing I found
that the way the clojure maven plugin launches java, it clobbers and `-D`
arguments passed in.
> 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
> Labels: newbie
>
> 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)
