Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1816#issuecomment-51654883
We definitely need to still run them even if the patch doesn't merge
cleanly. Sometimes people are working on a large patch that gets out of date
very frequently, e.g. every few hours, because it's a re-factoring or touches a
lot of code. It's a huge burden to require them to update the patch to run unit
tests - instead it's more efficient if they get it in working order, then merge
it and try again.
I sort of like just putting all of the statuses at the very end (except the
thing of "I'm starting tests"). Because for a reviewer there is only one thing
for them to sign off on.
---
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]
