rpl.rpl_stm_stop_middle_group failed in buildbot, server crashes

rpl.rpl_stm_stop_middle_group 'innodb,stmt' w1 [ fail ]

        Test ended at 2017-09-13 01:03:17

CURRENT_TEST: rpl.rpl_stm_stop_middle_group

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

included from ./include/wait_for_slave_param.inc at line 124:

included from ./include/wait_for_slave_sql_to_stop.inc at line 36:

included from ./extra/rpl_tests/rpl_stop_middle_group.test at line 124:

included from /mnt/buildbot/build/mariadb-10.2.9/mysql-test/suite/rpl/t/rpl_stm_stop_middle_group.test at line 11:

At line 62: query 'let $_include_file_connection= `SELECT SUBSTRING('$_include_file_connection', LENGTH('$_include_file_rpl_connection_name') + 2)`' failed: 2013: Lost connection to MySQL server during query

The result from queries just before the failure was:

< snip >

Last_SQL_Error	true

Fatal error: ... Slave SQL Thread stopped with incomplete event group having non-transactional changes. If the group consists solely of row-based events, you can try to restart the slave with --slave-exec-mode=IDEMPOTENT, which ignores duplicate key, key not found, and similar errors (see documentation for details).	1

select count(*) as one  from tm;

one

1

select count(*) as zero from ti;

zero

0

set @@global.debug_dbug="-d";

stop slave;

truncate table tm;

include/start_slave.inc

connection master;

connection slave;

set @@global.debug_dbug="+d,stop_slave_middle_group";

set @@global.debug_dbug="+d,incomplete_group_in_relay_log";

connection master;

update tm as t1, ti as t2 set t1.a=t1.a * 2, t2.a=t2.a * 2;

connection slave;

include/wait_for_slave_sql_to_stop.inc

2017-09-13  1:03:16 2896620352 [Note] Deleted Master_info file '/mnt/buildbot/build/mariadb-10.2.9/mysql-test/var/1/mysqld.2/data/master.info'.

2017-09-13  1:03:16 2896620352 [Note] Deleted Master_info file '/mnt/buildbot/build/mariadb-10.2.9/mysql-test/var/1/mysqld.2/data/relay-log.info'.

2017-09-13  1:03:16 2896620352 [Note] Master connection name: ''  Master_info_file: 'master.info'  Relay_info_file: 'relay-log.info'

2017-09-13  1:03:16 2896620352 [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='16040', master_log_file='master-bin.000001', master_log_pos='4'.

2017-09-13  1:03:16 2808769344 [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-09-13  1:03:16 2808466240 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 4, relay log './slave-relay-bin.000001' position: 4

2017-09-13  1:03:16 2808466240 [Warning] Slave SQL: Request to stop slave SQL Thread received while applying a group that has non-transactional changes; waiting for completion of the group ... , Gtid 0-1-4, Internal MariaDB error code: 0

2017-09-13  1:03:16 2808466240 [Warning] Slave SQL: Request to stop slave SQL Thread received while applying a group that has non-transactional changes; waiting for completion of the group ... , Gtid 0-1-4, Internal MariaDB error code: 0

2017-09-13  1:03:16 2808466240 [Warning] Slave SQL: Request to stop slave SQL Thread received while applying a group that has non-transactional changes; waiting for completion of the group ... , Gtid 0-1-4, Internal MariaDB error code: 0

2017-09-13  1:03:16 2808466240 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 1382

170913  1:03:16 [ERROR] mysqld got signal 11 ;

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.2.9-MariaDB-debug-log

key_buffer_size=1048576

read_buffer_size=131072

max_used_connections=4

max_threads=153

thread_count=12

It is possible that mysqld could use up to 

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

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

Thread pointer: 0xa73005d0

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

2017-09-13  1:03:16 2808466240 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 1382, relay log './slave-relay-bin.000002' position: 1682

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

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

[0xb76f4400]

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

/lib/i386-linux-gnu/libc.so.6(fnmatch+0x69)[0xb7260af9]

/mnt/buildbot/build/mariadb-10.2.9/sql/mysqld[0x8d179fa]

/mnt/buildbot/build/mariadb-10.2.9/sql/mysqld(_db_keyword_+0x79)[0x8d17ed2]

/mnt/buildbot/build/mariadb-10.2.9/sql/mysqld(_db_pargs_+0x65)[0x8d172e8]

2017-09-13  1:03:16 2808466240 [ERROR] Slave SQL: Fatal error: ... Slave SQL Thread stopped with incomplete event group having non-transactional changes. If the group consists solely of row-based events, you can try to restart the slave with --slave-exec-mode=IDEMPOTENT, which ignores duplicate key, key not found, and similar errors (see documentation for details). Gtid 0-1-7, Internal MariaDB error code: 1593

2017-09-13  1:03:16 2808466240 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 1634

/mnt/buildbot/build/mariadb-10.2.9/sql/mysqld(_ZN3THD11enter_stageEPK17PSI_stage_info_v1PKcS4_j+0x28)[0x827049a]

/mnt/buildbot/build/mariadb-10.2.9/sql/mysqld(_Z19close_thread_tablesP3THD+0x6c)[0x82cd755]

/mnt/buildbot/build/mariadb-10.2.9/sql/mysqld(_Z9reset_thdP3THD+0x1d)[0x82fdbe9]

2017-09-13  1:03:16 2808769344 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 1955

/mnt/buildbot/build/mariadb-10.2.9/sql/mysqld[0x88a2797]

2017-09-13  1:03:16 2808466240 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 1634, relay log './slave-relay-bin.000002' position: 1934

2017-09-13  1:03:16 2808769344 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16040',replication started in log 'master-bin.000001' at position 1955

/mnt/buildbot/build/mariadb-10.2.9/sql/mysqld[0x8a0ce92]

/mnt/buildbot/build/mariadb-10.2.9/sql/mysqld[0x899afbd]

/mnt/buildbot/build/mariadb-10.2.9/sql/mysqld[0x899b1c8]

/mnt/buildbot/build/mariadb-10.2.9/sql/mysqld[0x899b39e]

/mnt/buildbot/build/mariadb-10.2.9/sql/mysqld[0x8a59819]

/mnt/buildbot/build/mariadb-10.2.9/sql/mysqld[0x8a5999a]

2017-09-13  1:03:16 2808466240 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them Statement: update tm as t1, ti as t2 set t1.a=t1.a * 2, t2.a=t2.a * 2

2017-09-13  1:03:16 2808466240 [ERROR] Slave SQL: Fatal error: ... Slave SQL Thread stopped with incomplete event group having non-transactional changes. If the group consists solely of row-based events, you can try to restart the slave with --slave-exec-mode=IDEMPOTENT, which ignores duplicate key, key not found, and similar errors (see documentation for details). Gtid 0-1-8, Internal MariaDB error code: 1593

2017-09-13  1:03:16 2808466240 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 1955

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

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