Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/1816#issuecomment-51617033
Reposting here since the [original
thread](https://github.com/apache/spark/pull/1816#discussion_r15994082) is now
buried under an outdated commit.
Do we even want to run tests at all if a patch doesn't merge cleanly?
What's the point? Maybe it would be better if Jenkins complained right away and
said he wasn't gonna test the patch until it merged cleanly. What do you say
@pwendell?
Also, if the patch _does_ merge cleanly, would it make more sense to let
contributors know at start of the test cycle that they are adding new public
classes, as opposed to at the end like we do now?
---
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]
