Github user squito commented on the issue:
https://github.com/apache/spark/pull/13603
@kayousterhout sorry for the delays on my end, I've updated with the
requested changes. The check is now inside `TaskSetManager`, and I added a
test for the "unschedulablility" case I was describing. Though the behavior is
ust in `TaskSetManager`, I put the test in `TaskSchedulerImplSuite`, because
I'd like to push this test up to a slightly higher, more functional level, so
its easier to refactor etc. and keep the test. But if that is opening up a
larger discussion, I can just push it to `TaskSetManagerSuite` instead.
I also found something kinda weird about `TaskSchedulerImpl` I'll comment
on inline, mostly unrelated to this change.
---
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]
