Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9624#issuecomment-156915513
Isn't `spark-submit`'s default behavior to use a shared Ivy cache? If so,
shouldn't we be testing with that as the default rather than the exception so
that any bugs which are painful for users are equally painful for us, too? My
fear is that if there is somehow a corruption issue then we'll be masking it by
not using the shared cache in our own tests. Basically, I'm arguing that the
the shared cache in tests should be an opt-out feature, not opt-in.
---
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]
