s3.debug test failure

CURRENT_TEST: s3.debug

--- /usr/share/mysql/mysql-test/suite/s3/debug.result	2026-06-02 11:27:50.000000000 +0000

+++ /dev/shm/s3/13/log/debug.reject	2026-06-02 11:51:43.656691898 +0000

@@ -24,9 +24,9 @@

 count(*)

 100

 set @@global.s3_debug=0;

-FOUND 8 /s3_test_/ in mysqld.1.err

+FOUND 10 /s3_test_/ in mysqld.1.err

 select count(*) from t1;

 count(*)

 100

 drop table t1;

-FOUND 8 /s3_test_/ in mysqld.1.err

+FOUND 10 /s3_test_/ in mysqld.1.err

Result length mismatch

 - skipping '/dev/shm/s3/13/log/s3.debug/'

Test s3.debug has failed 2 times, no more retries!

s3.mysqldump                             w14 [ pass ]   1013

MTR's internal check of the test case 's3.mysqldump' failed.

This means that the test case does not preserve the state that existed

before the test case was executed.  Most likely the test case did not

do a proper clean-up. It could also be caused by the previous test run

by this thread, if the server wasn't restarted.

This is the diff of the states of the servers before and after the

test case was executed:

mysqltest: Logging to '/dev/shm/s3/14/tmp/check-mysqld_1.log'.

mysqltest: Results saved in '/dev/shm/s3/14/tmp/check-mysqld_1.result'.

mysqltest: Connecting to server localhost:19360 (socket /dev/shm/s3/tmp/14/mysqld.1.sock) as 'root', connection 'default', attempt 0 ...

mysqltest: ... Connected.

mysqltest: Start processing test commands from './include/check-testcase.test' ...

mysqltest: ... Done processing test commands.

--- /dev/shm/s3/14/tmp/check-mysqld_1.result	2026-06-02 11:51:42.393699568 +0000

+++ /dev/shm/s3/14/tmp/check-mysqld_1.reject	2026-06-02 11:51:43.668691825 +0000

@@ -597,7 +597,6 @@

 def	sys	utf8mb3	utf8mb3_general_ci	NULL	

 def	test	latin1	latin1_swedish_ci	NULL	

 tables_in_test

-t1

 tables_in_mysql

 mysql.columns_priv

 mysql.column_stats

Result length mismatch

not ok