You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by "Rick Moritz (JIRA)" <ji...@apache.org> on 2015/09/22 18:43:04 UTC
[jira] [Created] (ZEPPELIN-319) RemoteSchedulerTest can fail
depending on performance/timing
Rick Moritz created ZEPPELIN-319:
------------------------------------
Summary: RemoteSchedulerTest can fail depending on performance/timing
Key: ZEPPELIN-319
URL: https://issues.apache.org/jira/browse/ZEPPELIN-319
Project: Zeppelin
Issue Type: Bug
Components: build
Affects Versions: 0.5.0
Environment: High OS load/latency
Reporter: Rick Moritz
Priority: Trivial
I'm currently trying to get building Zeppelin's 0.5.0 stable, and stumbled across another intermittent failure:
RemoteSchedulerTest.java$L121''s assertion failed randomly, I presume because the 500ms thread sleep before was insufficient. I will provide a patch adding another 500ms should the first comparison fail, before asserting, in order to have a quick build in the normal case, with minimal waiting, and a slower build, should there b a performance issue. While not a perfect solution, this is probably the best hope to avoid broken builds for no reason with a higher probability.
I'm assuming that this error is also present in master, at least the relevant source code is identical.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)