mariadb/mysql-test/suite/rpl/t/rpl_row_conflicts.test
Michael Widenius eb75edfb2b Instead of writing "Errcode" to the log for Slave errors, use "Internal MariaDB error code"
This makes it clear that the error code has nothing to do with errno.


mysql-test/include/mtr_warnings.sql:
  Fixed suppression for new slave error messages
mysql-test/lib/My/Test.pm:
  Use 'send' instead of 'print' to avoid errors about "wrong class ... back attempt"
mysql-test/lib/v1/mtr_report.pl:
  Fixed suppression for new slave error messages
mysql-test/mysql-test-run.pl:
  Fixed suppression for new slave error messages
  Removed warning from perl 5.16.2 about arrays
mysql-test/r/flush_read_lock.result:
  Fixed suppression for new slave error messages
sql/rpl_reporting.cc:
  Instead of writing "Errcode" to the log for Slave errors, use "Internal MariaDB error code"
2013-05-03 01:54:47 +03:00

34 lines
975 B
Text

# See the top of mysql-test/extra/rpl_tests/rpl_conflicts.test for
# explanation of what this test does.
#
# This test file is for row-logging mode. It runs the test twice, with
# slave_exec_mode=STRICT and slave_exec_mode=IDEMPOTENT, respectively.
source include/have_binlog_format_row.inc;
source include/master-slave.inc;
connection slave;
call mtr.add_suppression("Slave: Can\'t find record in \'t1\' error.* .*");
call mtr.add_suppression("Can't find record in 't.'");
--echo [on slave]
connection slave;
SET @old_slave_exec_mode= @@global.slave_exec_mode;
--echo ######## Run with slave_exec_mode=STRICT ########
SET @@global.slave_exec_mode = 'STRICT';
source extra/rpl_tests/rpl_conflicts.test;
--source include/rpl_reset.inc
--echo ######## Run with slave_exec_mode=IDEMPOTENT ########
set @@global.slave_exec_mode= 'IDEMPOTENT';
source extra/rpl_tests/rpl_conflicts.test;
SET @@global.slave_exec_mode= @old_slave_exec_mode;
--source include/rpl_end.inc