Michael Widenius added a comment - 2016-08-21 21:41 The issue is that when running with valgrind, the test takes 500 seconds with InnoDB and 5000 seconds with xtradb. This causes wait_for_pos() to timeout in the rpl_mdev6020 test. Fixed by increasing wait_for_pos() timeout when running with valgrind. As the test takes so long with xtradb, I have disabled the test for now when run with valgrind

Elena Stepanova added a comment - 2016-08-22 00:34 As of Aug 17, it was also still failing with the assertion failure on 10.0. rpl.rpl_mdev6020 'mix,xtradb' w2 [ fail ] Test ended at 2016-08-17 08:04:17   CURRENT_TEST: rpl.rpl_mdev6020 Error: Packets out of order (Found: 0, expected 1) Error: Packets out of order (Found: 0, expected 1) Error: Packets out of order (Found: 0, expected 1) mysqltest: At line 43: failed in 'select master_pos_wait('master-bin.000002', 327, 300, '')': 2013: Lost connection to MySQL server during query   The result from queries just before the failure was: include/master-slave.inc [connection master] include/stop_slave.inc include/rpl_stop_server.inc [server_number=1] include/rpl_start_server.inc [server_number=1] SET SQL_LOG_BIN=0; ALTER TABLE mysql.gtid_slave_pos ENGINE = InnoDB; SET SQL_LOG_BIN=1; SET @old_engine= @@GLOBAL.default_storage_engine; SET GLOBAL default_storage_engine=InnoDB; SET @old_parallel= @@GLOBAL.slave_parallel_threads; SET GLOBAL slave_parallel_threads=12; CHANGE MASTER TO master_host='127.0.0.1', master_port=SERVER_MYPORT_1, master_user='root', master_log_file='master-bin.000001', master_log_pos=4; include/start_slave.inc SET SQL_LOG_BIN=0; ALTER TABLE mysql.gtid_slave_pos ENGINE = InnoDB; SET SQL_LOG_BIN=1;     Server [mysqld.2 - pid: 405, winpid: 405, exit: 256] failed during test run Server log from this test: ----------SERVER LOG START----------- 160817 8:04:04 [Note] /opt/buildbot-slave/mariadb/dan_demeter1/build/sql/mysqld (mysqld 10.0.27-MariaDB-debug) starting as process 406 ... 160817 8:04:04 [Note] Plugin 'ARCHIVE' is disabled. 160817 8:04:04 [Note] Plugin 'SEQUENCE' is disabled. 160817 8:04:04 [Note] Plugin 'CONNECT' is disabled. 160817 8:04:04 [Note] Plugin 'TEST_SQL_DISCOVERY' is disabled. 160817 8:04:04 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.   160817 8:04:04 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2016-08-17 08:04:04 7ff37f7dc780 InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!! 2016-08-17 08:04:04 7ff37f7dc780 InnoDB: !!!!!!!! UNIV_SYNC_DEBUG switched on !!!!!!!!! 160817 8:04:04 [Note] InnoDB: The InnoDB memory heap is disabled 160817 8:04:04 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 160817 8:04:04 [Note] InnoDB: Memory barrier is not used 160817 8:04:04 [Note] InnoDB: Compressed tables use zlib 1.2.8 160817 8:04:04 [Note] InnoDB: Using CPU crc32 instructions 160817 8:04:04 [Note] InnoDB: Initializing buffer pool, size = 8.0M 160817 8:04:04 [Note] InnoDB: Completed initialization of buffer pool 160817 8:04:04 [Note] InnoDB: Highest supported file format is Barracuda. 160817 8:04:05 [Note] InnoDB: 128 rollback segment(s) are active. 160817 8:04:05 [Note] InnoDB: Waiting for purge to start 160817 8:04:05 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.31-77.0 started; log sequence number 1629444 160817 8:04:05 [Note] Plugin 'XTRADB_READ_VIEW' is disabled. 160817 8:04:05 [Note] Plugin 'XTRADB_INTERNAL_HASH_TABLES' is disabled. 160817 8:04:05 [Note] Plugin 'XTRADB_RSEG' is disabled. 160817 8:04:05 [Note] Plugin 'INNODB_LOCK_WAITS' is disabled. 160817 8:04:05 [Note] Plugin 'INNODB_CMP_RESET' is disabled. 160817 8:04:05 [Note] Plugin 'INNODB_CMPMEM_RESET' is disabled. 160817 8:04:05 [Note] Plugin 'INNODB_CMP_PER_INDEX_RESET' is disabled. 160817 8:04:05 [Note] Plugin 'INNODB_FT_DEFAULT_STOPWORD' is disabled. 160817 8:04:05 [Note] Plugin 'INNODB_FT_DELETED' is disabled. 160817 8:04:05 [Note] Plugin 'INNODB_FT_BEING_DELETED' is disabled. 160817 8:04:05 [Note] Plugin 'INNODB_FT_CONFIG' is disabled. 160817 8:04:05 [Note] Plugin 'INNODB_FT_INDEX_CACHE' is disabled. 160817 8:04:05 [Note] Plugin 'INNODB_FT_INDEX_TABLE' is disabled. 160817 8:04:05 [Note] Plugin 'INNODB_SYS_TABLESTATS' is disabled. 160817 8:04:05 [Note] Plugin 'INNODB_SYS_INDEXES' is disabled. 160817 8:04:05 [Note] Plugin 'INNODB_SYS_COLUMNS' is disabled. 160817 8:04:05 [Note] Plugin 'INNODB_SYS_FIELDS' is disabled. 160817 8:04:05 [Note] Plugin 'INNODB_SYS_TABLESPACES' is disabled. 160817 8:04:05 [Note] Plugin 'INNODB_SYS_DATAFILES' is disabled. 160817 8:04:05 [Note] Plugin 'INNODB_CHANGED_PAGES' is disabled. 160817 8:04:05 [Note] Plugin 'SPHINX' is disabled. 160817 8:04:05 [Note] Plugin 'BLACKHOLE' is disabled. 160817 8:04:05 [Note] Plugin 'FEDERATED' is disabled. 160817 8:04:05 [Note] Plugin 'METADATA_LOCK_INFO' is disabled. 160817 8:04:05 [Note] Plugin 'FEEDBACK' is disabled. 160817 8:04:05 [Note] Plugin 'QUERY_RESPONSE_TIME' is disabled. 160817 8:04:05 [Note] Plugin 'QUERY_RESPONSE_TIME_AUDIT' is disabled. 160817 8:04:05 [Note] Plugin 'LOCALES' is disabled. 160817 8:04:05 [Note] Plugin 'rpl_semi_sync_master' is disabled. 160817 8:04:05 [Note] Plugin 'rpl_semi_sync_slave' is disabled. 160817 8:04:05 [Note] Plugin 'QUERY_CACHE_INFO' is disabled. 160817 8:04:05 [Note] Plugin 'unix_socket' is disabled. 160817 8:04:05 [Note] Server socket created on IP: '127.0.0.1'. 160817 8:04:05 [Note] /opt/buildbot-slave/mariadb/dan_demeter1/build/sql/mysqld: ready for connections. Version: '10.0.27-MariaDB-debug' socket: '/opt/buildbot-slave/mariadb/dan_demeter1/build/mysql-test/var/tmp/2/mysqld.2.sock' port: 16001 Source distribution 160817 8:04:06 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='', master_port='3306', master_log_file='', master_log_pos='4'. New state master_host='127.0.0.1', master_port='16000', master_log_file='master-bin.000001', master_log_pos='4'. 160817 8:04:06 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication started in log 'master-bin.000001' at position 4 160817 8:04:06 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 4, relay log './slave-relay-bin.000001' position: 4 160817 8:04:06 [Note] Error reading relay log event: slave SQL thread was killed 160817 8:04:06 [ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013) 160817 8:04:06 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 313 160817 8:04:11 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='127.0.0.1', master_port='16000', master_log_file='master-bin.000001', master_log_pos='313'. New state master_host='127.0.0.1', master_port='16000', master_log_file='master-bin.000001', master_log_pos='4'. 160817 8:04:11 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication started in log 'master-bin.000001' at position 4 160817 8:04:11 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 4, relay log './slave-relay-bin.000001' position: 4 mysqld: /opt/buildbot-slave/mariadb/dan_demeter1/build/sql/mdl.cc:2409: bool MDL_context::acquire_lock(MDL_request*, ulong): Assertion `(mdl_request->type != MDL_INTENTION_EXCLUSIVE && mdl_request->type != MDL_EXCLUSIVE) || !(get_thd()->rgi_slave && get_thd()->rgi_slave->is_parallel_exec && lock->check_if_conflicting_replication_locks(this))' failed. 160817 8:04:16 [ERROR] mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware.   To report this bug, see https://mariadb.com/kb/en/reporting-bugs   We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail.   Server version: 10.0.27-MariaDB-debug key_buffer_size=1048576 read_buffer_size=131072 max_used_connections=4 max_threads=153 thread_count=4 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 62846 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.   Thread pointer: 0x0x7ff31c000b00 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0x7ff36c717db8 thread_stack 0x48000 mysys/stacktrace.c:268(my_print_stacktrace)[0xd5ce19] sql/signal_handler.cc:159(handle_fatal_signal)[0x765775] /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7ff37ed63340] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39)[0x7ff37e1a4cc9] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7ff37e1a80d8] /lib/x86_64-linux-gnu/libc.so.6(+0x2fb86)[0x7ff37e19db86] /lib/x86_64-linux-gnu/libc.so.6(+0x2fc32)[0x7ff37e19dc32] sql/mdl.cc:2405(MDL_context::acquire_lock(MDL_request*, unsigned long))[0x6d4d3b] sql/mdl.cc:2621(MDL_context::upgrade_shared_lock(MDL_ticket*, enum_mdl_type, unsigned long))[0x6d5277] sql/sql_base.cc:1823(wait_while_table_is_used(THD*, TABLE*, ha_extra_function))[0x5988b6] sql/sql_table.cc:8146(simple_rename_or_index_change)[0x67d3e1] sql/sql_alter.cc:314(Sql_cmd_alter_table::execute(THD*))[0x6ccfdd] sql/sql_parse.cc:5115(mysql_execute_command(THD*))[0x5e7d2b] sql/sql_parse.cc:6575(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x5f0d47] sql/log_event.cc:4365(Query_log_event::do_apply_event(rpl_group_info*, char const*, unsigned int))[0x844a19] sql/log_event.h:1360(Log_event::apply_event(rpl_group_info*))[0x56b17c] include/my_atomic.h:210(my_atomic_add64)[0x70c493] sql/rpl_parallel.cc:1201(handle_rpl_parallel_thread)[0x710871] perfschema/pfs.cc:1863(pfs_spawn_thread)[0x97ef09] /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7ff37ed5b182] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7ff37e26847d]   Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7ff2f8064e2b): ALTER TABLE `table100_int_autoinc` ENABLE KEYS Connection ID (thread ID): 12 Status: NOT_KILLED   Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on   The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. Writing a core file ----------SERVER LOG END-------------     - saving '/opt/buildbot-slave/mariadb/dan_demeter1/build/mysql-test/var/2/log/rpl.rpl_mdev6020-mix,xtradb/' to '/opt/buildbot-slave/mariadb/dan_demeter1/build/mysql-test/var/log/rpl.rpl_mdev6020-mix,xtradb/'   Retrying test rpl.rpl_mdev6020, attempt(2/3)...   worker[2] > Restart - not started worker[2] > Restart - not started ***Warnings generated in error logs during shutdown after running tests: rpl.rpl_mdev6020   mysqld: /opt/buildbot-slave/mariadb/dan_demeter1/build/sql/mdl.cc:2409: bool MDL_context::acquire_lock(MDL_request*, ulong): Assertion `(mdl_request->type != MDL_INTENTION_EXCLUSIVE && mdl_request->type != MDL_EXCLUSIVE) || !(get_thd()->rgi_slave && get_thd()->rgi_slave->is_parallel_exec && lock->check_if_conflicting_replication_locks(this))' failed. Attempting backtrace. You can use the following information to find out

Michael Widenius added a comment - 2018-05-17 16:05 Comment from Elena: From cross-reference, it looks like that particular failure was happening on the specific builder p8-trusty-bintar [almost?] exclusively, so it stopped happening in early 2017, apparently when that builder was removed or modified. The test was still failing a lot, but on different reasons. Then, suddenly the same failure happened once at the very end of 2017, on kvm-bintar-trusty-amd64, on some development tree, and for now that's all