Comment 2 for bug 1832360

Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

So turns out the test case is being a little naughty by comparing floats with a "==", which s390x in particular does not handling so well.

You can see in the debug log that the test float value is set to 17.0815f but actually gets stored as '17.081499', '17.081501' and '17.081503' in various places.

Ideally the test should be comparing floats by difference within the bounds of an epsilon.

Preparing a patch for this now.