rpl.rpl_slow_query_log fails

CURRENT_TEST: rpl.rpl_slow_query_log

mysqltest: At line 299: "Assertion failed! Master and slave slow log contents differ. Bailing out!"

The result from queries just before the failure was:

< snip >

**** Now do inserts again, but first add an index to the table.

**** Outcome: Note that the slave contains the same one entry (as

****          the master does)  whereas before the patch it did not.

********************************************************************

ALTER TABLE t1 ADD INDEX id1(a);

INSERT INTO t1 values(1, sleep(3));

connection slave;

connection master;

***********************************************

** DUMPING MASTER SLOW LOG CONTENTS

***********************************************

SELECT * FROM mysql.slow_log;

start_time      user_host       query_time      lock_time       rows_sent       rows_examined   db      last_insert_id insert_id        server_id       sql_text        thread_id       rows_affected

2025-08-25 17:04:06.028382      root[root] @ localhost [127.0.0.1]      00:00:03.002006 00:00:00.000632 0       0      test     0       0       1       INSERT INTO t1 values(1, sleep(3))      8       1

connection slave;

***********************************************

** DUMPING SLAVE SLOW LOG CONTENTS

***********************************************

SELECT * FROM mysql.slow_log;

start_time      user_host       query_time      lock_time       rows_sent       rows_examined   db      last_insert_id insert_id        server_id       sql_text        thread_id       rows_affected

More results from queries before failure can be found in /home/parad/mariadb/10.11-0/b/mysql-test/var/log/rpl_slow_query_log.log

 - saving '/home/parad/mariadb/10.11-0/b/mysql-test/var/log/rpl.rpl_slow_query_log-stmt/' to '/home/parad/mariadb/10.11-0/b/mysql-test/var/log/rpl.rpl_slow_query_log-stmt/'

***Warnings generated in error logs during shutdown after running tests: rpl.rpl_slow_query_log

2025-08-25 17:03:47 8 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system function that may return a different value on the slave. Statement: INSERT INTO t1 values(1, sleep(3))

2025-08-25 17:04:03 8 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system function that may return a different value on the slave. Statement: INSERT INTO t1 values(1, sleep(3))

2025-08-25 17:04:09 8 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system function that may return a different value on the slave. Statement: INSERT INTO t1 values(1, sleep(3))

2025-08-25 17:03:50 11 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system function that may return a different value on the slave. Statement: INSERT INTO t1 values(1, sleep(3))

2025-08-25 17:04:06 19 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system function that may return a different value on the slave. Statement: INSERT INTO t1 values(1, sleep(3))

2025-08-25 17:04:12 19 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it uses a system function that may return a different value on the slave. Statement: INSERT INTO t1 values(1, sleep(3))