Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1716
@cloverhearts thank you for contribution! In my experience, if PR author or
one of reviewers post the reason for CI failure - that speeds up the
review\merge process dramatically.
CI is failing with flaky pySpark tests, not relevant to the PR
```
Results :
Failed tests:
ZeppelinSparkClusterTest.pySparkDepLoaderTest:430 expected:<FINISHED> but
was:<ERROR>
ZeppelinSparkClusterTest.pySparkAutoConvertOptionTest:312
expected:<FINISHED> but was:<ERROR>
Tests run: 82, Failures: 2, Errors: 0, Skipped: 1
```
It will be handled under
[ZEPPELIN-1761](https://issues.apache.org/jira/browse/ZEPPELIN-1761).
\cc @felizbear to review the frontend part.
---
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.
---
