Github user markhamstra commented on the issue:
https://github.com/apache/spark/pull/19468
> iron out the kinks
A large chunk of the difficulty in identifying and ironing out kinks in
such a project is the difficulty of writing adequate tests of the scheduler
code. I'd expect test coverage to take roughly the same amount of effort as all
of the rest of the scheduler plug-in effort.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
