Github user srowen commented on the issue:
https://github.com/apache/spark/pull/22893
Heh, as a side effect, this made the output of computeCost more accurate in
one Pyspark test. It prints "2.0" rather than "2.000..." I think you can change
the three instances that failed to just expect "2.0".--- --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
