Am 20.01.2017 um 20:26 schrieb Sergei Golubchik:
Hi, Reindl!
On Jan 20, Reindl Harald wrote:
looks like many of them are caused by "--mysqld=--binlog-format=mixed" but without a ton of tests are skipped with "Neither MIXED nor STATEMENT binlog format" what i really don't understand when you configure and start mysqld scripted
binlog.binlog_mysqlbinlog-cp932 'row' [ skipped ] Neither MIXED nor STATEMENT binlog format
Okay, that's what I actually suspected after your first email, when 'row' and 'stmt' combinations weren't skipped as the should've been.
Our mysql-test-run.pl does not skip tests with this message. It used to, in MySQL times, but I've changed that many years ago.
MySQL's mysql-test-run.pl still has this behavior.
You're using MySQL's mysql-test-run.pl with our tests
are you kidding me? [root@testserver:~]$ cat /usr/local/bin/mysql-test.sh #!/usr/bin/dash /usr/bin/su -c 'cd /usr/share/mysql-test; ./mysql-test-run.pl --parallel=1 --max-test-fail=0 --force' mysql rm -rf /usr/share/mysql-test/var/* [root@testserver:~]$ rpm -q --file /usr/share/mysql-test mariadb-test-10.1.21-3.fc24.20170120.rh.x86_64