Github user squito commented on the issue:
https://github.com/apache/spark/pull/13603
actually, calling it a flaky test is unfair -- really spark itself was
flaky, the behavior was not reliable when you had locality + blacklists, you
might think the taskSet was unschedulable, though it just hadn't scheduled
anything on some executors yet due to locality. I added a test for that
specifically:
https://github.com/apache/spark/pull/13603/commits/635edec9072585d2232d97c085ef60f39fddaafa
I also just merged in the changes
https://github.com/apache/spark/pull/13826, so that should be reviewed first.
---
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]
