[MDEV-25095] innodb_gis test failure: Result length mismatch Created: 2021-03-09 Updated: 2023-04-27 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | GIS, Tests |
| Affects Version/s: | 10.3.28, 10.4.18, 10.5.9 |
| Fix Version/s: | 10.4, 10.5, 10.6 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Thomas Deutschmann | Assignee: | Oleksandr Byelkin |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Portage 3.0.13 (python 3.8.7-final-0, default/linux/amd64/17.1, gcc-9.3.0, glibc-2.31-r7, 5.11.0-gentoo-x86_64 x86_64) |
||
| Description |
|
I am very sure that these tests passed last week when I pushed updated mariadb ebuilds for Gentoo. |
| Comments |
| Comment by Marko Mäkelä [ 2021-03-09 ] | |||||||||||||||||||||||||||||||||||
|
Floating point differences can be somewhat of a mystery. Did something change in the compiler or in the compilation options? I suppose that in this case we could try to apply some rounding in the query or tweak the test case in some other way (see | |||||||||||||||||||||||||||||||||||
| Comment by Thomas Deutschmann [ 2021-03-10 ] | |||||||||||||||||||||||||||||||||||
|
No, nothing suspicious in toolchain changed. I was able to restore state from 2021-02-23 when I added the new versions to Gentoo and where tests passed: So I would appreciate if we could make these tests more stable by adding rounding if possible. | |||||||||||||||||||||||||||||||||||
| Comment by Sergei Golubchik [ 2021-04-14 ] | |||||||||||||||||||||||||||||||||||
|
I'd expect results to be stable. string↔double conversion is stable. math depends on the toolchain, compiler version, set of optimizations enabled. If none of that has changed, results should really be stable. | |||||||||||||||||||||||||||||||||||
| Comment by Thomas Deutschmann [ 2021-11-14 ] | |||||||||||||||||||||||||||||||||||
|
With mariadb-10.6.5, main.gis test is failing on AMD processors, too:
|