Details
Description
This is the only test that does source include/have_32bit.inc. And the latter uses @@version_compile_machine like '%64%' which, apparently, works incorrectly on s390x.
Fix:
- remove include/have_32bit.inc and its counterpart include/have_64bit.inc
- combine suite/sys_vars/t/innodb_ft_result_cache_limit_32.test and suite/sys_vars/t/innodb_ft_result_cache_limit_64.test into one test file that includes word_size.inc
See, for example, suite/sys_vars/t/sysvars_innodb.test
All builds made from commit https://salsa.debian.org/mariadb-team/mariadb-10.1/commit/f0256238130cb7f3cdb3c711940a036673502566 (branch "stretch") passed at https://launchpad.net/~mysql-ubuntu/+archive/ubuntu/mariadb-10.1/+builds?build_text=&build_state=all
One s390x builds made from commit https://salsa.debian.org/mariadb-team/mariadb-10.1/commit/516a8e1ca92828cff78a450365d08a7764546e5d (branch "ubuntu-18.04") failed at https://launchpadlibrarian.net/422045160/buildlog_ubuntu-bionic-s390x.mariadb-10.1_1%3A10.1.39-0ubuntu0.18.04.1~ubuntu18.04.1~1556873841.516a8e1ca9_BUILDING.txt.gz with
}}
sys_vars.innodb_ft_result_cache_limit_32 'innodb_plugin' w4 [ fail ]
Test ended at 2019-05-03 09:30:50
CURRENT_TEST: sys_vars.innodb_ft_result_cache_limit_32
--- /<<PKGBUILDDIR>>/mysql-test/suite/sys_vars/r/innodb_ft_result_cache_limit_32.result 2019-04-30 21:10:12.000000000 +0000
+++ /<<PKGBUILDDIR>>/mysql-test/suite/sys_vars/r/innodb_ft_result_cache_limit_32.reject 2019-05-03 09:30:50.446198129 +0000
@@ -1,7 +1,5 @@
set global innodb_ft_result_cache_limit=5000000000;
-Warnings:
-Warning 1292 Truncated incorrect innodb_ft_result_cache_limit value: '5000000000'
select @@innodb_ft_result_cache_limit;
@@innodb_ft_result_cache_limit
-4294967295
+5000000000
set global innodb_ft_result_cache_limit=2000000000;
{{