Am 20.01.2017 um 17:21 schrieb Sergei Golubchik:
Hi, Reindl!
I cannot repeat this. I get:
rpl.rpl_binlog_index 'row' [ skipped ] Not ROW format rpl.sec_behind_master-5114 'stmt' [ skipped ] Not STATEMENT format rpl.rpl_semi_sync_event_after_sync 'innodb,mix' [ pass ] 10470
they are failing here for many years see alo the mess about enrcytion - instead realize "oh, it's not there" which happens at begin at llops through all tests, all of them failing and waits each time some seconds _______________________________ something similar happend when you built without partition support as my changelog of the rpm package shows [root@srv-rhsoft:~]$ rpm -q --changelog mariadb-server | grep -i partition - enable partition because too much auto-test problems _______________________________ encryption.innodb_encryption 'xtradb' [ skipped ] Test requires InnoDB. 2017-01-20 17:09:37 140411189942592 [ERROR] InnoDB: cannot enable encryption, encryption plugin is not available 2017-01-20 17:09:37 140411189942592 [ERROR] Plugin 'InnoDB' init function returned error. 2017-01-20 17:09:37 140411189942592 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. worker[1] mysql-test-run: WARNING: Process [mysqld.1 - pid: 9910, winpid: 9910, exit: 1792] died after mysql-test-run waited 3.2 seconds for /usr/share/mysql-test/var/run/mysqld.1.pid to be created. encryption.tempfiles 'cbc,xtradb' [ fail ] Test ended at 2017-01-20 17:10:27 CURRENT_TEST: encryption.tempfiles Failed to start mysqld.1 mysqltest failed but provided no output - saving '/usr/share/mysql-test/var/log/encryption.tempfiles-cbc,xtradb/' to '/usr/share/mysql-test/var/log/encryption.tempfiles-cbc,xtradb/' ***Warnings generated in error logs during shutdown after running tests: encryption.tempfiles 2017-01-20 17:10:25 140290260609344 [ERROR] /usr/libexec/mysqld: unknown variable 'file-key-management-encryption-algorithm=aes_cbc' 2017-01-20 17:10:25 140290260609344 [ERROR] Aborting worker[1] mysql-test-run: WARNING: Process [mysqld.1 - pid: 9933, winpid: 9933, exit: 1792] died after mysql-test-run waited 3.3 seconds for /usr/share/mysql-test/var/run/mysqld.1.pid to be created. encryption.tempfiles 'ctr,xtradb' [ fail ] Test ended at 2017-01-20 17:10:31 CURRENT_TEST: encryption.tempfiles CURRENT_TEST: encryption.tempfiles Failed to start mysqld.1 - saving '/usr/share/mysql-test/var/log/encryption.tempfiles-ctr,xtradb/' to '/usr/share/mysql-test/var/log/encryption.tempfiles-ctr,xtradb/' ***Warnings generated in error logs during shutdown after running tests: encryption.tempfiles 2017-01-20 17:10:28 139721608362304 [ERROR] /usr/libexec/mysqld: unknown variable 'file-key-management-encryption-algorithm=aes_ctr' 2017-01-20 17:10:28 139721608362304 [ERROR] Aborting encryption.innodb-page_encryption-32k 'cbc,xtradb' [ fail ] Test ended at 2017-01-20 17:12:57 CURRENT_TEST: encryption.innodb-page_encryption-32k Failed to start mysqld.1 mysqltest failed but provided no output - saving '/usr/share/mysql-test/var/log/encryption.innodb-page_encryption-32k-cbc,xtradb/' to '/usr/share/mysql-test/var/log/encryption.innodb-page_encryption-32k-cbc,xtradb/' ***Warnings generated in error logs during shutdown after running tests: encryption.innodb-page_encryption-32k 2017-01-20 17:12:55 140523870546240 [ERROR] /usr/libexec/mysqld: unknown variable 'file-key-management-encryption-algorithm=aes_cbc' 2017-01-20 17:12:55 140523870546240 [ERROR] Aborting worker[1] mysql-test-run: WARNING: Process [mysqld.1 - pid: 12568, winpid: 12568, exit: 1792] died after mysql-test-run waited 3.2 seconds for /usr/share/mysql-test/var/run/mysqld.1.pid to be created. encryption.innodb-page_encryption-32k 'ctr,xtradb' [ fail ] Test ended at 2017-01-20 17:13:01 CURRENT_TEST: encryption.innodb-page_encryption-32k CURRENT_TEST: encryption.innodb-page_encryption-32k Failed to start mysqld.1
(it's innodb in my build, but that shouldn't matter). The first two tests should not even be started, because you run your tests with --mysqld=--binlog-format=mixed, so mysql-test-run.pl will skip tests with 'row' and 'stmt' without executing a single line from them. I don't know what can possibly go wrong for this functionality not to work. It doesn't depend on replication, it doesn't depend on the server or build options, it's just loading the combination file and skipping combinations that don't match the specified command-line option. I've never seen it misbehaving.
On Jan 20, Reindl Harald wrote:
shouldn't the testsuite at some point in time run without errors? "run STOP SLAVE '' first" - uhm did i start it? it's scripted by shipped scripts
[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 --mysqld=--binlog-format=mixed --force' mysql rm -rf /usr/share/mysql-test/var/*
rpl.rpl_binlog_index 'row' [ fail ] Test ended at 2017-01-20 16:56:16 CURRENT_TEST: rpl.rpl_binlog_index mysqltest: In included file "./include/rpl_init.inc": included from ./include/master-slave.inc at line 38: included from /usr/share/mysql-test/suite/rpl/t/rpl_binlog_index.test at line 20: At line 165: query 'SET GLOBAL gtid_slave_pos= ""' failed: 1198: This operation cannot be performed as you have a running slave ''; run STOP SLAVE '' first The result from queries just before the failure was: include/master-slave.inc - saving '/usr/share/mysql-test/var/log/rpl.rpl_binlog_index-row/' to '/usr/share/mysql-test/var/log/rpl.rpl_binlog_index-row/'
rpl.sec_behind_master-5114 'stmt' [ fail ] Test ended at 2017-01-20 16:58:33 CURRENT_TEST: rpl.sec_behind_master-5114 mysqltest: In included file "./include/rpl_init.inc": included from ./include/master-slave.inc at line 38: included from /usr/share/mysql-test/suite/rpl/t/sec_behind_master-5114.test at line 1: At line 165: query 'SET GLOBAL gtid_slave_pos= ""' failed: 1198: This operation cannot be performed as you have a running slave ''; run STOP SLAVE '' first The result from queries just before the failure was: include/master-slave.inc
rpl.rpl_semi_sync_event_after_sync 'mix,xtradb' [ fail ] Test ended at 2017-01-20 16:59:24 CURRENT_TEST: rpl.rpl_semi_sync_event_after_sync mysqltest: At line 1: query 'set global rpl_semi_sync_master_wait_point=AFTER_SYNC' failed: 1193: Unknown system variable 'rpl_semi_sync_master_wait_point' The result from queries just before the failure was: set global rpl_semi_sync_master_wait_point=AFTER_SYNC; - saving '/usr/share/mysql-test/var/log/rpl.rpl_semi_sync_event_after_sync-mix,xtradb/' to '/usr/share/mysql-test/var/log/rpl.rpl_semi_sync_event_after_sync-mix,xtradb/'
Regards, Sergei Chief Architect MariaDB and security@mariadb.org
-- Reindl Harald the lounge interactive design GmbH A-1060 Vienna, Hofmühlgasse 17 CTO / CISO / Software-Development m: +43 676 40 221 40 p: +43 1 595 3999 33 http://www.thelounge.net/