[debian-mysql] Bug#1029374: Acknowledgement (mariadb: FTBFS on ppc64: main.func_json_notembedded very long output and crash)

[Otto Kekäläinen]

On a rerun in https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=ppc64&ver=1%3A10.11.1-4&stamp=1676050342&raw=0
the same main.stat_tables_innodb passed but we saw the same corruption
error on another test:

main.stat_tables_innodb 'innodb'         w6 [ pass ]  39106

main.mysql_upgrade 'innodb'              w5 [ fail ]
        Test ended at 2023-02-10 17:28:14
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 494:
At line 15: exec of '/<<PKGBUILDDIR>>/builddir/client//mariadb-dump
--defaults-file=/<<PKGBUILDDIR>>/builddir/mysql-test/var/5/my.cnf
--defaults-group-suffix=.1 mysql >
/<<PKGBUILDDIR>>/builddir/mysql-test/var/tmp/5/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.");
***Warnings generated in error logs during shutdown after running
tests: main.mysql_upgrade
2023-02-10 17:28:04 0 [ERROR] InnoDB: Database page corruption on disk
or a failed read of file './ibdata1' page [page id: space=0, page
number=219]. You may have to recover from a backup.
2023-02-10 17:28:04 0 [ERROR] InnoDB: File './ibdata1' is corrupted
2023-02-10 17:28:04 0 [ERROR] InnoDB: Database page corruption on disk
or a failed read of file './ibdata1' page [page id: space=0, page
number=219]. You may have to recover from a backup.