Description of problem:
Testcase main.gis-precise from testsuite (mariadb-test package) is failling on s390x
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run /usr/share/mysql-test/mysql-test-run main.gis-precise
Failure: Failed 1/1 tests, 0.00% were successful.
Failing test(s): main.gis-precise
This is a known bug already spotted in bug #906746 and thus it is disabled now in a test-suite run during build.
Upstream report is here:
So let's keep this bug open to track that issue.
Some more light on what is wrong there:
Test case gis-precise fails on ppc, ppc64, s390 and s390x platforms. Generally, some integer values are not print as integers again, but as a very similar real number.
The minimal reproducer can be:
select astext(ST_UNION(GeomFromText('POLYGON((0 0, 50 45, 40 50, 0 0))'), GeomFromText('LINESTRING(-10 -10, 200 200, 199 201, -11 -9)')));
This has the following output on x86_64:
GEOMETRYCOLLECTION(LINESTRING(-10 -10,0 0),LINESTRING(-11 -9,8 10),POLYGON((0 0,40 50,50 45,0 0)),LINESTRING(46.666666666666664 46.666666666666664,200 200,199 201,45.33333333333333 47.33333333333333))
but on other arches:
GEOMETRYCOLLECTION(LINESTRING(-10 -10,0 0),LINESTRING(-11 -9,7.999999999999999 10),POLYGON((0 0,40 50,50 45,0 0)),LINESTRING(46.666666666666664 46.666666666666664,200 200,199 201,45.33333333333333 47.33333333333333))
This issue is caused by different precision on different arches, which shouldn't have any consequences in practice. Setting Devel Cond NAK unless we have an idea how to solve this.
Moving to RHEL-7.1. We would like to fix this but even upstream doesn't know how. It's probably matter of test suite only; no serious issues should be encountered while usage, since a little different precision is common on different architectures.
Same issue on AArch64.
Same issue on ppc64le
The test above passed during last build (fixed upstream).
Removing CondNAK and providing devel_ack+. Vasku, can you, please, provide qe_ack+? It's fixed upstream anyway, so it's more for the sake of adding the bug to erratum.
I'm not Vašek and I'm not providing qe_ack but rather qa_ack, but hope I've satisfied you anyways :-)
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.