Github user mgaido91 commented on the issue:
https://github.com/apache/spark/pull/19480
sorry, the test failure is due to an OutOfMemory exception. I don't know
whether it is possible to change the heap size used by sbt in the Jenkins job
and I am not sure this is the right thing to do.
The problem is caused by the UT which reproduces the error in a end-to-end
example. Nonetheless, there is the first UT I added which tests that the patch
is working. IMHO we might get rid of this new UT and rely on the original one
in order not to waste resources.
Let me know what you think about this and what I should do.
Thanks.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
