Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/23236
Thanks for a close look, @BryanCutler. I just increased the timeout because
I was just trying to keep the test as is and fix it. The actual test doesn't
look taking so much time but it looks it can be flaky when the resource usage
is heavy. If you feel this can be resolved in other ways, would you mind if I
ask to take a look for this please? and i'm happy to close this one. Actually,
I am not quite familiar with ML ones ..
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
