Github user vkaggalumn commented on the pull request:
https://github.com/apache/storm/pull/122#issuecomment-73368488
@harshach Sorry for the delay in my response.
Thanks for your response. I had already tried to pass STORM_TEST_TIMEOUT_MS
at runtime (Run Configuration-
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
Github user vkaggalumn commented on the pull request:
https://github.com/apache/storm/pull/122#issuecomment-71032607
Thanks @harshach.
If I am reading the documentation right, I see the following which
instructs how to build the storm code base with the STORM_TEST_TIMEOUT_MS
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/122#issuecomment-70688283
https://github.com/apache/storm/blob/master/storm-core/src/clj/backtype/storm/testing.clj#L190-192
Shows that the environment variable STORM_TEST_TIMEOUT_MS, can
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/122#issuecomment-70689189
@revans2 its in DEVELOPER.md
https://github.com/apache/storm/blob/master/DEVELOPER.md#build-the-code-and-run-the-tests
---
If your project is set up for it, you can
Github user vkaggalumn commented on the pull request:
https://github.com/apache/storm/pull/122#issuecomment-70396115
Hello!
I am also wondering on how to set this parameter in java? Would somebody
comment please?
Thanks
---
If your project is set up for it, you can
