Github user squito commented on the pull request:
https://github.com/apache/spark/pull/4220#issuecomment-71923273
I kinda see what is going on with the tests now. A [test case in
SparkSubmitSuite](https://github.com/apache/spark/blob/master/core/src/test/scala/org/apache/spark/deploy/SparkSubmitSuite.scala#L91)
adds a non-existent jar to the system properties. That property never gets
cleared, so later jobs which should submit successfully, are still trying to
load that jar.
I don't understand how your change is effecting this, though, or how this
ever worked before. Maybe this change is exposing some lurking error --
something which just "happened" to work before. It seems like having multiple
apps futzing w/ the system properties at the same time is bound to create
problems.
---
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
