[SPARK-2479][MLlib] Comparing floating-point numbers using relative error in UnitTests

Floating point math is not exact, and most floating-point numbers end up being slightly imprecise due to rounding errors. Simple values like 0.1 cannot be precisely represented using binary floating point numbers, and the limited precision of floating point numbers means that slight changes in the order of operations or the precision of intermediates can change the result. That means that comparing two floats to see if they are equal is usually not what we want. As long as this imprecision stays small, it can usually be ignored.
See the following famous article for detail.
http://randomascii.wordpress.com/2012/02/25/comparing-floating-point-numbers-2012-edition/
For example:
float a = 0.15 + 0.15
float b = 0.1 + 0.2
if(a == b) // can be false!
if(a >= b) // can also be false!

(ps, not all the tests involving floating point comparisons are changed to use almostEquals) 

Authors: 
  DB Tsai <dbtsai@alpinenow.com>
  Marek Kolodziej <marek@alpinenow.com>
See commentary at https://issues.apache.org/jira/browse/SPARK-2599?focusedCommentId=14068293&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14068293 I can see the idea here, but all of these kinds of efforts seem to lead to errors or unintuitive behavior. For example this line means that:

Fails:
expected = 1e-15
actual = 2e-15
eps = 0.1

Passes:
expected = 1e-16
actual = 2e-16
eps = 0.1

Why is 1e-15 special anyway?