Summary of current status of https://ci.debian.net/packages/m/mariadb/
## ppc64el Last passed in https://ci.debian.net/packages/m/mariadb/testing/ppc64el/40870773/ where 1048 tests were successful: MariaDB: 1:10.6.11-1 kernel: Linux 6.5.0-0.deb12.4-powerpc64le The log above includes 4 variants of main.innodb_ext_key passing. Later we see: Completed: Failed 8/1053 tests, 99.24% were successful. Failing test(s): main.innodb_ext_key main.stat_tables_innodb main.xa_prepared_binlog_off Completed: Failed 11/1055 tests, 98.96% were successful. Failing test(s): main.innodb_ext_key main.subselect_sj2_jcl6 Completed: Failed 3/1050 tests, 99.71% were successful. Failing test(s): main.innodb_ext_key Completed: Failed 2/1049 tests, 99.81% were successful. Failing test(s): main.innodb_ext_key Completed: Failed 3/1050 tests, 99.71% were successful. Failing test(s): main.xa_prepared_binlog_off Completed: Failed 10/1054 tests, 99.05% were successful. Failing test(s): main.innodb_ext_key main.subselect MariaDB: 1:10.6.11-1 kernel: Linux 6.5.0-0.deb12.4-powerpc64le In https://ci.debian.net/packages/m/mariadb/testing/ppc64el/40894691/ we see: Completed: All 1048 tests were successful. Errors/warnings were found in logfiles during server shutdown after running the following sequence(s) of tests: main.long_unique_bugs 183 tests were skipped, 76 by the test itself. The test emitted a MariaDB crash: main.long_unique_bugs 'innodb' w1 [ pass ] 324 14:51:15 [ERROR] mysqld got signal 11 ; Attempting backtrace. You can use the following information to find out Since 2023-12-18 16:13:06 UTC the test has failed to even start. The ppc64el logs have crashes and most likely due to https://jira.mariadb.org/browse/MDEV-30728, in particular the main.innodb_ext_key one.