Github user squito commented on the issue:
https://github.com/apache/spark/pull/14079
the last test failure was from a rare and pre-existing race in the
`SchedulerIntegration` asserts. I couldn't recreate it on my laptop in 1000
runs, but in any case I handed it here:
https://github.com/apache/spark/pull/14079/commits/5d8500a948ee7a2df5b59bef71bc0a52fc4f04de.
I actually wonder if this is desired behavior -- is it OK for the
`DAGScheduler` to mark a stage as completed before the `TaskScheduler` does?
Though it is unusual and surprising, from a look through the code I couldn't
see any potential harm, so I left the possibility there and just handled it in
the test.
---
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]
