Github user koeninger commented on the issue:
https://github.com/apache/spark/pull/15355
I have generally been unable to reproduce these kinds of test failures on
my local environment, and don't have access to the build server, so trying fix
without repro is pretty much shooting randomly in the dark. It does seem
unfortunate to me that we're effectively doing full integration tests on every
PR, even if a patch has changed something (e.g. MLLib) that couldn't possibly
affect the modules in /external
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
