Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15706
@seyfe so my guess is that, not surprisingly, this is some pretty arcane
interaction between several of a) codegen, b) Netty's class hierarchy, c) SBT
vs Maven classloading and d) the spark-shell's classloading peculiarities.
I strongly suspect it's an issue with the test of course, not the
underlying change. I wonder if we can just write a different test that doesn't
trip this.
Is it necessary to test this in the REPL? can we just write the code it
tests as a test directly?
---
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]
