Github user ejono commented on the issue:
https://github.com/apache/zeppelin/pull/1880
@felixcheung, yes, I was referring to
PySparkInterpreterTest.testCompletion, which I thought may have been broken in
the new Spark 2.1 Travis CI profile because it was broken for that profile but
not other profiles, and it was broken for me locally as well when using Spark
2.1. @zjffdu says that it is a flaky test though, so I have no concerns if
that's the case.
---
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.
---
