Bug#22923426 LOG_FILE_SIZE_1 FAILS TO REPORT INNODB: CANNOT RESIZE LOG FILES IN READ-ONLY

The InnoDB change buffer is deleted lazily in a background task.
If a previously completed test has caused something to remain in
the InnoDB change buffer on the server instance, restarting the
server with --innodb-read-only would be refused with an unexpected
error message:

"Change buffer must be empty when --innodb-read-only is set."

This WL#6494 test is expecting another error message, for InnoDB
refusing to resize the InnoDB redo logs in read-only mode.

The test failed to initiate a slow shutdown (forcing a change buffer merge)
before restarting the server in --innodb-read-only mode.

Reviewed-by: Vinay Fisrekar <[email protected]>

Author: Marko Mäkelä

mysql-test/suite/innodb/r/innodb-log-file-size-1.result

@@ -153,6 +153,7 @@ id	LEFT(bfield,20)
 21	aaaaaaaaaaaaaaaaaaaa
 22	bbbbbbbbbbbbbbbbbbbb
 23	cccccccccccccccccccc
+SET GLOBAL innodb_fast_shutdown=0;
 "test misc 1"
 "test misc 2"
 "test misc 3"

mysql-test/suite/innodb/t/innodb-log-file-size-1.test

@@ -198,6 +198,7 @@ let SEARCH_FILE= $MYSQLTEST_VARDIR/log/my_restart.err;
 let $args=--loose-console > $SEARCH_FILE 2>&1;
 
 # Stop the server
+SET GLOBAL innodb_fast_shutdown=0;
 let $restart_file= $MYSQLTEST_VARDIR/tmp/mysqld.1.expect;
 --exec echo "wait" > $restart_file
 --shutdown_server