Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/316#issuecomment-63486189
Hello.
To understand the reason, please reference STORM-492.
Actually test time is affected to user machine rather than test complexity,
so fixed timeout value is unusable.
On 2014ë
11ì 18ì¼ (í) at ì¤í 11:24 Ahmet DAL
<[email protected]> wrote:
> Custom test timeout with variable TEST-TIMEOUT-MS was being defined with
> System Environment Variable. This cause a problem to define it on every
> test simply. System property is now being used to define custom
> TEST-TIMEOUT-MS variable value. This can be simply set before every test
as
>
> System.setProperty("STORM_TEST_TIMEOUT_MS", "20000");
> ------------------------------
> You can merge this Pull Request by running
>
> git pull https://github.com/javrasya/storm master
>
> Or view, comment on, or merge it at:
>
> https://github.com/apache/storm/pull/316
> Commit Summary
>
> - Custom TEST-TIMEOUT-MS Definition Method Changed
>
> File Changes
>
> - *M* storm-core/src/clj/backtype/storm/testing.clj
> <https://github.com/apache/storm/pull/316/files#diff-0> (2)
>
> Patch Links:
>
> - https://github.com/apache/storm/pull/316.patch
> - https://github.com/apache/storm/pull/316.diff
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/storm/pull/316>.
>
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
