Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/17144
I'm not really the right person to review this code, but that being said,
I'm not crazy about this fix, because 1s is kind of a long time to consistently
wait. It's better for tests to continually check a condition and then timeout
after some time -- this allows the test to complete quickly in the normal case,
but still give some leeway for when Jenkins is busy. What about instead
wrapping the condition in the second part of the test in an eventually block,
and then giving that a more generous timeout (e.g., a few seconds)?
---
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]
