[
https://issues.apache.org/jira/browse/STORM-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14287627#comment-14287627
]
ASF GitHub Bot commented on STORM-354:
--------------------------------------
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/122#issuecomment-71040715
@vkaggalumn I don't think we tested that part of dev cycle. Its definitely
a valid use case. Most of the time storm tests timeout in a build env for unit
tests when a user running all the test suite.
I just poked around eclipse you can add Environment variable under Run
configurations for a project or set a system wide environment variable for
STORM_TEST_TIMEOUT_MS.
> Allow users to pass TEST-TIMEOUT-MS as param for complete-topology
> ------------------------------------------------------------------
>
> Key: STORM-354
> URL: https://issues.apache.org/jira/browse/STORM-354
> Project: Apache Storm
> Issue Type: Improvement
> Affects Versions: 0.9.2-incubating
> Reporter: Aaron Levin
> Assignee: Aaron Levin
> Priority: Minor
> Labels: test
> Fix For: 0.9.3
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> It would be nice if complete-topology allowed a user to pass in the default
> timeout as a parameter (rather than just setting it as 5000ms). I had a test
> that kept failing by taking too long.
> This PR adds functionality without breaking any existing code. Tests pass.
> (PS - not sure if this is the proper way to submit a PR for an apache
> project. I'm open to feedback. Thanks)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
