mariadb/mysql-test/t/rpl_variables.test
unknown e4e7f8c385 bug#34427 slave misses rendezvous in rpl_variables
There was no instruction in the test that enforces the slave successfully connect
to the master.
The way the test was been written allowed the slave to had been late for rendezvous 
so that about-connecting time queries to the master failed and are error-logged
to had been seen in Warnings of pb.

Fixed with adding a sychronization primitive to the test.
No test case is possible, observe error logs on pb.

Todo: revise need of rpl_report.pl's rules due to failing execution of
queries from get_master_verion_and_clock().
Any test should try to use a synchornization primitive like the current fix
makes and do not let the slave to miss successful connecting.


mysql-test/t/rpl_variables.test:
  Completing the test's body with a synch macro to not let
  the slave to miss the successful connecting to the master.
2008-02-08 21:03:10 +02:00

27 lines
811 B
Text

source include/master-slave.inc;
connection master;
# Init for rstore of variable values
set @my_slave_net_timeout =@@global.slave_net_timeout;
set global slave_net_timeout=100;
set global sql_slave_skip_counter=100;
# End of 4.1 tests
# BUG #7800: Add various-slave related variables to SHOW VARIABLES
show variables like 'slave_compressed_protocol';
--replace_column 2 SLAVE_LOAD_TMPDIR
show variables like 'slave_load_tmpdir';
# We just set some arbitrary values in variables-master.opt so we can test
# that a list of values works correctly
show variables like 'slave_skip_errors';
# Restore touched values
set global slave_net_timeout =@my_slave_net_timeout;
# bug#34427 slave misses rendezvous
# don't let the master be shut down until the slave has connected
sync_slave_with_master;