Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1487
@zjffdu I've missed remove some scripts in `testing`. I'll fix it.
Concerning the modes, in an early stage of Spark, there're some different
behaviours of different modes, thus we need to test Zeppelin with Spark in a
standalone cluster, but for now, Spark become stable and if different modes
have different behaviours, it's definitely Spark's problem and Spark should fix
it. Thus I don't think we need to test Zeppelin a cluster mode. Furthermore,
personally, I don't know what benefit we have in a different test environment
between local and CI. In case of Python, I've experienced that some tests only
failed in CI, not in a local with different setting between them. I think we
should try to keep both environments equally.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
