Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/9075#issuecomment-148659530
Yeah, we have to fix it for branch 1.5 with a small fix like this.
Is it possible to test this with unit tests? Could you check if there are
unit tests of the DAGScheduler / TaskScheduler that we can use to unit test so
that something like this does not happen ever again.
---
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]
