Bug#905829: mozjs52: tests fail on sparc64: numeric operations expecting NaN get undefined instead
Lots of mozjs52 tests fail on sparc64 because the test does some numeric
operation that expects NaN (not a number) as result, but gets undefined
back instead, for example:
FAILED! Number.NEGATIVE_INFINITY % Number.NEGATIVE_INFINITY = undefined expected: NaN
FAILED! VAR1 =-Infinity; VAR2=-Infinity; VAR1 %= VAR2; VAR1 = undefined expected: NaN
FAILED! [reported from top level script] testfunc : Expected value 'NaN', Actual value 'undefined'
Does sparc64 have an unusual binary representation of NaN and undefined
John Paul Adrian Glaubitz asked me to mark sparc64 as one of the
architectures where build-time test failures are ignored, which I will do
when I have a bug number for this that I can refer to.