memory allocation errors on Windows ARM64 CI

innodb.innodb_bulk_create_index_replication 'mix' w8 [ fail ]

        Test ended at 2026-05-21 09:04:47

CURRENT_TEST: innodb.innodb_bulk_create_index_replication

mysqltest: At line 61: query 'CREATE INDEX idx_title ON t1(title)' failed: ER_OUT_OF_RESOURCES (1041): Out of memory.

The result from queries just before the failure was:

< snip >

INSERT INTO t1 VALUES (i, i, CONCAT('a', i));

END IF;

IF i%2 != 0 AND load_even != 1 THEN

INSERT INTO t1 VALUES (i, i, CONCAT('a', i));

END IF;

SET i = i + 1;

END WHILE;

COMMIT;

END|

CREATE TABLE t1(

class	INT,

id	INT,

title	VARCHAR(100)

) ENGINE=InnoDB ;

SELECT COUNT(*) FROM t1;

COUNT(*)

50

/* Create index. */

CREATE INDEX idx_id ON t1(id);

CREATE INDEX idx_title ON t1(title);

More results from queries before failure can be found in C:\Users\runneradmin\AppData\Local\Temp\ci\var\8\log\innodb_bulk_create_index_replication.log

 - saving 'C:/Users/runneradmin/AppData/Local/Temp/ci/var/8/log/innodb.innodb_bulk_create_index_replication-mix/' to 'C:/Users/runneradmin/AppData/Local/Temp/ci/var/log/innodb.innodb_bulk_create_index_replication-mix/'

main.ctype_ujis                          w6 [ pass ]  12660

MTR's internal check of the test case 'main.ctype_ujis' 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:

***Warnings generated in error logs during shutdown after running tests: innodb.innodb_bulk_create_index_replication

Warning: 1  9:04:42 7 [Warning] Slave: Out of memory. Error_code: 1041