CURRENT_TEST: innodb.innodb_defrag_concurrent

--- /home/jenkins/workspace/Source-Build-Test/src/mysql-test/suite/innodb/r/innodb_defrag_concurrent.result	2022-12-05 04:16:31.000000000 +0000

+++ /home/jenkins/workspace/Source-Build-Test/src/mysql-test/suite/innodb/r/innodb_defrag_concurrent.reject	2022-12-05 04:41:33.845583397 +0000

@@ -77,6 +77,7 @@

 test.t1	optimize	status	OK

 check table t1 extended;

 Table	Op	Msg_type	Msg_text

+test.t1	check	Warning	InnoDB: Unpurged clustered index record in table `test`.`t1`: COMPACT RECORD(info_bits=32, 8 fields): {[4]    (0x80000001),[6]      (0x00000000F4BA),[7]p      (0x70000002AB0EEA),[256]AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA(0x414141414141414141414141414141414141414141414141414141414141414141414

 test.t1	check	status	OK

 select count(*) from t1;

 count(*)

The tree

origin/bb-11.1-MDEV-30545 e1e007f9fbb0538b05a3f3b3e2ad8eb94a14391b 2023-03-06T16:47:24+02:00

behaved well during RQG testing.

The problems met are already known and in the main tree too.