Source: mariadb Version: 1:10.11.5-1 Tags: upstream, confirmed, help, ftbfs X-Debbugs-CC: debian-powe...@lists.debian.org User: debian-powe...@lists.debian.org Usertags: ppc64
Builds on ppc64 repeatedly failed on test main.mysql_upgrade with error message: main.mysql_upgrade 'innodb' w8 [ fail ] Test ended at 2023-10-04 05:48:24 CURRENT_TEST: main.mysql_upgrade mariadb-dump: Couldn't execute 'show create table `transaction_registry`': Unknown storage engine 'InnoDB' (1286) mysqltest: In included file "./include/load_dump_and_upgrade.inc": included from /<<PKGBUILDDIR>>/mysql-test/main/mysql_upgrade.test at line 507: At line 15: exec of '/<<PKGBUILDDIR>>/builddir/client//mariadb-dump --defaults-file=/<<PKGBUILDDIR>>/builddir/mysql-test/var/8/my.cnf --defaults-group-suffix=.1 mysql > /<<PKGBUILDDIR>>/builddir/mysql-test/var/tmp/8/mysql_database_backup' failed, error: 512, status: 2, errno: 11 Output from before failure: call mtr.add_suppression("Column count of mysql.proc is wrong. Expected 21, found 20."); The result from queries just before the failure was: < snip > Phase 8/8: Running 'FLUSH PRIVILEGES' OK SHOW CREATE USER mariadb_102; CREATE USER for mariadb_102@% CREATE USER `mariadb_102`@`%` connect con1,localhost,mariadb_102; select current_user(); current_user() mariadb_102@% disconnect con1; connection default; drop table mysql.global_priv; rename table mysql.global_priv_bak to mysql.global_priv; # End of 10.4 tests # # Check that mysql_upgrade can be run on mysqldump # of mysql schema from previous versions # call mtr.add_suppression("innodb_(table|index)_stats has length mismatch in the column name table_name"); call mtr.add_suppression("Column count of mysql.proc is wrong. Expected 21, found 20."); This seems to hint at some bug that the mariadb-upgrade perhaps didn't run properly on this platform. Full logs: * https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=ppc64&ver=1%3A10.11.5-1&stamp=1696398960&raw=0 * https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=ppc64&ver=1%3A10.11.5-1&stamp=1696469091&raw=0 These logs also show failures in tests main.xa_prepared_binlog_off, main.statistics_upgrade_not_done, main.greedy_optimizer with errors hinting too disk issue / file corruption, but those failures were sporadic. The test main.mysql_upgrade was passing in the 10.11.4-1 builds on Debian unstable, so this is clearly a regression in 10.11.5.