rpl.rpl_stm_flsh_tbls fails in buildbot

rpl.rpl_stm_flsh_tbls 'mix'              w1 [ fail ]

        Test ended at 2017-08-16 01:12:48

CURRENT_TEST: rpl.rpl_stm_flsh_tbls

mysqltest: In included file "./include/rpl_sync.inc": 

included from ./include/rpl_end.inc at line 80:

included from ./extra/rpl_tests/rpl_flsh_tbls.test at line 67:

included from /mnt/buildbot/build/mariadb-10.3.1/mysql-test/suite/rpl/t/rpl_stm_flsh_tbls.test at line 7:

At line 157: failed in 'select master_pos_wait('master-bin.000001', 1900, 300, '')': 2013: Lost connection to MySQL server during query

The result from queries just before the failure was:

< snip >

a

flush tables;

connection slave;

select * from t3;

a

stop slave;

include/wait_for_slave_to_stop.inc

connection master;

drop table t1;

connection slave;

flush tables with read lock;

start slave;

include/wait_for_slave_param.inc [Slave_IO_Running]

include/wait_for_slave_sql_to_start.inc

stop slave;

ERROR HY000: Can't execute the given command because you have active locked tables or an active transaction

unlock tables;

connection master;

drop table t3, t4, t5;

include/rpl_end.inc

More results from queries before failure can be found in /mnt/buildbot/build/mariadb-10.3.1/mysql-test/var/1/log/rpl_stm_flsh_tbls.log

Server [mysqld.2 - pid: 26153, winpid: 26153, exit: 256] failed during test run

Server log from this test:

----------SERVER LOG START-----------

2017-08-16  1:12:46 2896620352 [Note] Deleted Master_info file '/run/shm/var_auto_gZ1V/1/mysqld.2/data/master.info'.

2017-08-16  1:12:46 2896620352 [Note] Deleted Master_info file '/run/shm/var_auto_gZ1V/1/mysqld.2/data/relay-log.info'.

2017-08-16  1:12:46 2896620352 [Note] Master connection name: ''  Master_info_file: 'master.info'  Relay_info_file: 'relay-log.info'

2017-08-16  1:12:46 2896620352 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='127.0.0.1', master_port='16040', master_log_file='', master_log_pos='4'. New state master_host='127.0.0.1', master_port='16040', master_log_file='master-bin.000001', master_log_pos='4'.

2017-08-16  1:12:46 2842340160 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16040',replication started in log 'master-bin.000001' at position 4

2017-08-16  1:12:46 2842037056 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 4, relay log './slave-relay-bin.000001' position: 4

2017-08-16  1:12:46 2842037056 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-16  1:12:46 2842037056 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 1590

2017-08-16  1:12:46 2842340160 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 1590

2017-08-16  1:12:46 2842037056 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 1590, relay log './slave-relay-bin.000002' position: 1890

2017-08-16  1:12:46 2842340160 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16040',replication started in log 'master-bin.000001' at position 1590

mysqld: /home/buildbot/buildbot/build/mariadb-10.3.1/sql/sql_base.cc:204: uint get_table_def_key(const TABLE_LIST*, const char**): Assertion `!strcmp(table_list->get_db_name(), table_list->mdl_request.key.db_name()) && !strcmp(table_list->get_table_name(), table_list->mdl_request.key.name())' failed.

170816  1:12:46 [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.3.1-MariaDB-debug-log

key_buffer_size=1048576

read_buffer_size=131072

max_used_connections=4

max_threads=153

thread_count=13

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61882 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0xb0317ac8

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 = 0xa96aa220 thread_stack 0x49000

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld(my_print_stacktrace+0x32)[0x8d7dcce]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld(handle_fatal_signal+0x3c7)[0x8628e2b]

[0xb76f8400]

[0xb76f8424]

/lib/i386-linux-gnu/libc.so.6(gsignal+0x4f)[0xb71d41ef]

/lib/i386-linux-gnu/libc.so.6(abort+0x175)[0xb71d7835]

/lib/i386-linux-gnu/libc.so.6(+0x27095)[0xb71cd095]

/lib/i386-linux-gnu/libc.so.6(+0x27147)[0xb71cd147]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld(_Z17get_table_def_keyPK10TABLE_LISTPPKc+0x97)[0x83055c0]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld(_Z17tdc_acquire_shareP3THDP10TABLE_LISTjPP5TABLE+0x25)[0x8579f3a]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld(_Z10open_tableP3THDP10TABLE_LISTP18Open_table_context+0x979)[0x8308442]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld[0x830b1b2]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld(_Z11open_tablesP3THDRK14DDL_options_stPP10TABLE_LISTPjjP19Prelocking_strategy+0x299)[0x830c0bf]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld(_Z20open_and_lock_tablesP3THDRK14DDL_options_stP10TABLE_LISTbjP19Prelocking_strategy+0xbe)[0x830d59f]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld(_Z20open_and_lock_tablesP3THDP10TABLE_LISTbj+0x5c)[0x83012c6]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld(_ZN15rpl_slave_state11record_gtidEP3THDPK8rpl_gtidybbPPv+0x252)[0x852dc6a]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld(_ZN15rpl_slave_state4loadEP3THDPKcjbb+0xff)[0x852f3d1]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld[0x82c8bbe]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld(handle_slave_io+0x8bc)[0x82cfdd6]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld[0x883d558]

/lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xb7480d4c]

/lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0xb7290ace]

Trying to get some variables.

Some pointers may be invalid and cause the dump to abort.

Query (0x0): 

Connection ID (thread ID): 48

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,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_grouping_derived=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-------------