bug#37605: [core-updates] MariaDB fails tests on armhf-linux

[Marius Bakke]

"mariadb" consistently fails a single test on the core-updates branch on
armhf-linux:

https://ci.guix.gnu.org/build/1689172/details

The test output:

CURRENT_TEST: binlog_encryption.rpl_skip_replication
safe_process[21120]: parent_pid: 16023
safe_process[21120]: Started child 21121, terminated: 0
--- 
/tmp/guix-build-mariadb-10.1.41.drv-0/mariadb-10.1.41/mysql-test/suite/binlog_encryption/rpl_skip_replication.result
        1970-01-01 00:00:00.000000000 +0000
+++ 
/tmp/guix-build-mariadb-10.1.41.drv-0/mariadb-10.1.41/mysql-test/suite/binlog_encryption/rpl_skip_replication.reject
        2019-09-05 23:24:20.300000000 +0000
@@ -46,12 +46,15 @@
 Tables_in_test
 t1
 t2
+t3
 SELECT * FROM t1;
 a      b
 1      NULL
+2      NULL
 SELECT * FROM t2;
 a      b
 1      NULL
+2      NULL
 DROP TABLE t3;
 FLUSH NO_WRITE_TO_BINLOG LOGS;
 STOP SLAVE;
@@ -66,12 +69,17 @@
 Tables_in_test
 t1
 t2
+t3
 SELECT * FROM t1;
 a      b
 1      NULL
+2      NULL
+3      NULL
 SELECT * FROM t2;
 a      b
 1      NULL
+2      NULL
+3      NULL
 DROP TABLE t3;
 FLUSH NO_WRITE_TO_BINLOG LOGS;
 STOP SLAVE;
@@ -109,6 +117,7 @@
 SELECT * FROM t1 ORDER by a;
 a      b
 1      0
+2      0
 3      0
 TRUNCATE t1;
 STOP SLAVE;
@@ -127,6 +136,7 @@
 SET binlog_format= @old_binlog_format;
 SELECT * FROM t1;
 a      b
+3      5
 4      5
 include/stop_slave.inc
 SET @old_slave_binlog_format= @@global.binlog_format;
@@ -151,6 +161,7 @@
 2      8
 SELECT * FROM t1 ORDER by a;
 a      b
+1      8
 2      8
 include/stop_slave.inc
 SET GLOBAL binlog_format= @old_slave_binlog_format;
@@ -225,6 +236,7 @@
 START SLAVE;
 SELECT * FROM t1;
 a      b
+1      NULL
 2      NULL
 SET skip_replication= 0;
 TRUNCATE t1;

mysqltest: Result length mismatch

safe_process[21120]: Got signal 17, child_pid: 21121
safe_process[21120]: Killing child: 21121
safe_process[21120]: Child exit: 1

binlog_encryption.rpl_skip_replication 'mix,xtradb' w2 [ fail ]
        Test ended at 2019-09-05 23:24:22

This does not happen on current 'master', so the problem was introduced
somewhere in between ccbc1c5eb..cbc8c658d.

signature.asc
Description: PGP signature