CURRENT_TEST: sys_vars.rpl_init_slave_func
mysqltest: In included file "./include/assert.inc":
included from ./include/assert.inc at line 75:
At line 74: Test assertion failed in assert.inc
...
Assertion text: '@@global.max_connections = @start_max_connections'
Assertion condition: '@@global.max_connections = @start_max_connections'
Assertion condition, interpolated: '@@global.max_connections = @start_max_connections'
Assertion result: '0'
Assertion debug statement:
SELECT @@global.max_connections, @start_max_connections;
@@global.max_connections @start_max_connections
152 151
This shows that init_slave command has been executed already. It is possible because of a race condition: the slave SQL thread is set to running state very early in its initialisation, and before running the init_slave command. Thus, it's possible that the initial "source include/master-slave.inc;" pick up the command.
A new failure with extra diagnostics:
CURRENT_TEST: sys_vars. rpl_init_ slave_func assert. inc": assert. inc at line 75: max_connections = @start_ max_connections ' max_connections = @start_ max_connections ' max_connections = @start_ max_connections ' max_connections , @start_ max_connections ; max_connections @start_ max_connections
mysqltest: In included file "./include/
included from ./include/
At line 74: Test assertion failed in assert.inc
...
Assertion text: '@@global.
Assertion condition: '@@global.
Assertion condition, interpolated: '@@global.
Assertion result: '0'
Assertion debug statement:
SELECT @@global.
@@global.
152 151
This shows that init_slave command has been executed already. It is possible because of a race condition: the slave SQL thread is set to running state very early in its initialisation, and before running the init_slave command. Thus, it's possible that the initial "source include/ master- slave.inc; " pick up the command.