Bug #62155 binlog.binlog_stm_unsafe_warning fails when run with --repeat=2
Submitted: 12 Aug 2011 15:54 Modified: 10 Jan 2013 11:17
Reporter: Oleg Tsarev Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Tests Severity:S3 (Non-critical)
Version:5.1.59 OS:Any
Assigned to: CPU Architecture:Any

[12 Aug 2011 15:54] Oleg Tsarev 
Description:
--- /storage/dev/percona/repeat/bug_report/Percona-Server-5.1.58-rel12.9/mysql-test/suite/binlog/r/binlog_stm_unsafe_warning.result	2011-07-01 18:36:13.000000000 +0300
+++ /storage/dev/percona/repeat/bug_report/Percona-Server-5.1.58-rel12.9/mysql-test/suite/binlog/r/binlog_stm_unsafe_warning.reject	2011-08-12 18:53:51.170049619 +0300
@@ -47,4 +47,4 @@
 SET GLOBAL log_warnings = @old_log_warnings;
 # Count the number of times the "Unsafe" message was printed
 # to the error log.
-Occurrences: 1
+Occurrences: 2

How to repeat:
./mysql-test-run binlog_stm_unsafe_warning --repeat=2

Suggested fix:
https://code.launchpad.net/~tsarev/percona-server/binlog_stm_unsafe_warning-repeatable-fai...
[12 Aug 2011 16:51] Valeriy Kravchuk 
Thank you for the bug report. Verified with current mysql-5.1 from bzr on Mac OS X:

macbook-pro:mysql-test openxs$ ./mtr  binlog_stm_unsafe_warning --repeat=2
Logging: ./mtr  binlog_stm_unsafe_warning --repeat=2
110812 19:50:08 [Warning] Setting lower_case_table_names=2 because file system for /var/folders/dX/dXCzvuSlHX4Op1g-o1jIWk+++TI/-Tmp-/OzD8eJGAuV/ is case insensitive
110812 19:50:08 [Note] Plugin 'FEDERATED' is disabled.
110812 19:50:08 [Note] Plugin 'ndbcluster' is disabled.
MySQL Version 5.1.59
Checking supported features...
 - skipping ndbcluster
 - SSL connections supported
Collecting tests...
 - adding combinations for binlog
vardir: /Users/openxs/dbs/5.1/mysql-test/var
Checking leftover processes...
Removing old var directory...
Creating var directory '/Users/openxs/dbs/5.1/mysql-test/var'...
Installing system database...
Using server port 55021

==============================================================================

TEST                                      RESULT   TIME (ms)
------------------------------------------------------------

worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 13000..13009
binlog.binlog_stm_unsafe_warning 'mix'   [ skipped ]  Doesn't support --binlog-format='mixed'
binlog.binlog_stm_unsafe_warning 'row'   [ skipped ]  Doesn't support --binlog-format='row'
binlog.binlog_stm_unsafe_warning 'stmt'  [ pass ]   1204
binlog.binlog_stm_unsafe_warning 'stmt'  [ fail ]
        Test ended at 2011-08-12 19:50:18

CURRENT_TEST: binlog.binlog_stm_unsafe_warning
--- /Users/openxs/dbs/5.1/mysql-test/suite/binlog/r/binlog_stm_unsafe_warning.result	2011-08-10 22:51:10.000000000 +0300
+++ /Users/openxs/dbs/5.1/mysql-test/suite/binlog/r/binlog_stm_unsafe_warning.reject	2011-08-12 19:50:18.000000000 +0300
@@ -47,4 +47,4 @@
 SET GLOBAL log_warnings = @old_log_warnings;
 # Count the number of times the "Unsafe" message was printed
 # to the error log.
-Occurrences: 1
+Occurrences: 2

mysqltest: Result content mismatch

 - saving '/Users/openxs/dbs/5.1/mysql-test/var/log/binlog.binlog_stm_unsafe_warning-stmt/' to '/Users/openxs/dbs/5.1/mysql-test/var/log/binlog.binlog_stm_unsafe_warning-stmt/'
------------------------------------------------------------
The servers were restarted 0 times
Spent 1.204 of 11 seconds executing testcases

Completed: Failed 1/2 tests, 50.00% were successful.

Failing test(s): binlog.binlog_stm_unsafe_warning

The log files in var/log may give you some hint of what went wrong.

If you want to report this error, please read first the documentation
at http://dev.mysql.com/doc/mysql/en/mysql-test-suite.html

mysql-test-run: *** ERROR: there were failing test cases
[10 Jan 2013 11:17] Erlend Dahl 
Fixed in 5.1.62