Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/5096#issuecomment-90356825
@andrewor14 I think the test failure is because of a SparkSubmit unit test
that is broken right now. If you see the test at
https://github.com/apache/spark/blob/e40ea8742a8771ecd46b182f45b5fcd8bd6dd725/core/src/test/scala/org/apache/spark/deploy/SparkSubmitSuite.scala#L97
we don't pass in a primaryResource or a mainClass and yet expect the
argument parsing to succeed. The test will exit at
https://github.com/apache/spark/blob/e40ea8742a8771ecd46b182f45b5fcd8bd6dd725/core/src/main/scala/org/apache/spark/deploy/SparkSubmitArguments.scala#L214
but we replace the `exitFn` and so it doesn't exit
Any good ideas on how to change the test case ? Should we just add a dummy
primary resource, main class to it ?
---
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]
