Github user rawkintrevo commented on the issue:
https://github.com/apache/zeppelin/pull/928
@bzz and @jongyoul
OK, so two things I think have happened. (In case some thing like this
happens again).
When I rebased, some version of ZeppelinClusterTest.java that had the
[PySpark tests commented
out](https://github.com/apache/zeppelin/pull/928/commits/d5963a9844ea9765ff2a34c5bcaf19f05a42d837#diff-64a9440e811c5fba6ac1b61157fa6912L121)
got worked in, so of course it passed, the failing tests were skipped.
However, I also happened to notice
[here](https://github.com/apache/zeppelin/pull/928/commits/d5963a9844ea9765ff2a34c5bcaf19f05a42d837#diff-69b17249ac9d265091d730130d973f4aR493)
that `org.apache.zeppelin.mahout.MahoutSparkInterpreter` was listed before
`org.apache.zeppelin.spark.PySparkInterpreter` so I move the Mahout one down,
and the tests seem to be passing now.
This led me to believe, that is a very fragile test that should be looked
into, but then I also realized I forgot to put a comma after the
MahoutSparkInterpreter, so I'm going to do that now, and I'll bet what was
happening, when it made the cluster: it didn't know how to make the pySpark or
any of the other interpreters because of the missing comma, so mystery solved.
Thanks for all of your help/sorry for wasting your time... I owe you both
beers next time we're in the same spot.
---
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.
---
