Github user preeze commented on the pull request:
https://github.com/apache/spark/pull/5835#issuecomment-102321139
For a reason I am still struggling to reproduce the failure locally and
thus can only guess about the real cause of the failing tests. But since we
both agree that SPARK-7527 is likely the guilty, it quite probably is indeed.
It would be very handy if both issues could be tackled at once. This is
what we tried and this is what didn't work unfortunately.
I agree with your scenario of moving forward faster by decoupling fixes
into separate pull-requests.
Before I proceed with reverting the fix for SPARK-7527, may I ask you a
couple of questions:
* How do I stop progress on Jira ticket for SPARK-7527 and unlink it from
the pull request?
* Given that _org.apache.spark.util.Utils#isInInterpreter_ is _slightly_
incorrect, do we still want to keep this logic in Utils or move it back to
ClosureCleaner?
PS I am sorry for being available these days a bit less than normally.
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
