Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2399#issuecomment-56368310
@pwendell `compute-classpath` will put test classes on the classpath for
`spark-submit` et al if `SPARK_TESTING=1`, which is set by test invocations.
This is how `SparkSubmitSuite` works for example, invoking its own
`SimpleApplicationTest` class which is in `src/test` too. I don't think that's
it, and don't see any use of `MasterFailureTest` except in `FailureSuite`.
Unless we're missing something else, I agree with @vanzin that this should
probably be merged (and main removed) as perhaps this is a hold-over from an
earlier usage of the test that is no longer applicable.
This PR just moves `MasterFailureTest` but I could go further if there's
agreement.
---
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
