Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/2685#issuecomment-61227318
@zhzhan Had a glance of the Kryo issue you pointed out should be related to
the POM inconsistency problem I mentioned above, but I'm not sure whether they
are identical since this issue doesn't mention any specific Kryo version. I'll
investigate this later. Although Jenkins finally nods, I'm still puzzled with
the root cause of the original build failure. (We only know that introducing
Kryo 2.22 prevents un-shaded Objenesis classes from being included in the
assembly jar and thus breaks the core tests, but how and why?)
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
