testcase rpl_gtid_split_statements is failing on trunk

Can you please post a sample crash stacktrace for crash stacktrace SEO?

Thank you for the report.

Test fails with regular trunk build with following stack trace:

sveta@Thinkie:~/build/ps-5.7/mysql-test$ ~/build/mysql-5.7/bin/mysqldump --innodb-optimize-keys
mysqldump: [ERROR] unknown option '--innodb-optimize-keys'
sveta@Thinkie:~/build/ps-5.7/mysql-test$ ./mtr rpl.rpl_gtid_split_statements --mysqld=--gtid_mode=on --mysqld=--enforce-gtid-consistency
Logging: ./mtr rpl.rpl_gtid_split_statements --mysqld=--gtid_mode=on --mysqld=--enforce-gtid-consistency
MySQL Version 5.7.20
Checking supported features...
 - SSL connections supported
 - binaries are debug compiled
Collecting tests...
 - adding combinations for rpl
Checking leftover processes...
Removing old var directory...
Creating var directory '/home/sveta/build/ps-5.7/mysql-test/var'...
Installing system database...
Using parallel: 1

==============================================================================

TEST RESULT TIME (ms) or COMMENT
--------------------------------------------------------------------------

worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 13000..13009
rpl.rpl_gtid_split_statements 'mix' [ skipped ] Doesn't support --binlog-format='mixed'
rpl.rpl_gtid_split_statements 'row' [ skipped ] Doesn't support --binlog-format='row'
rpl.rpl_gtid_split_statements 'stmt' [ fail ]
        Test ended at 2017-12-11 15:18:35

CURRENT_TEST: rpl.rpl_gtid_split_statements
mysqltest: In included file ./extra/rpl_tests/rpl_drop_multiple_tables.inc at line 86:
included from ./extra/rpl_tests/rpl_drop_multiple_tables_in_multiple_ways.inc at line 28:
included from ./extra/rpl_tests/rpl_split_statements.test at line 242:
included from /home/sveta/build/ps-5.7/mysql-test/suite/rpl/t/rpl_gtid_split_statements.test at line 3:
At line 86: query 'DROP TABLE $table_list' failed with wrong errno 2013: 'Lost connection to MySQL server during query', instead of 1884...

The result from queries just before the failure was:
include/master-slave.inc
Warnings:
Note #### Sending passwords in plain text without SSL/TLS is extremely insecure.
Note #### Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
[connection master]
CALL mtr.add_suppression('Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT.');
CALL mtr.add_suppression('Cannot execute statement because it needs to be written to the binary log as multiple statements');
CALL mtr.add_suppression('DROP DATABASE failed; some tables may have been dropped but the database directory remains.');
CALL mtr.add_suppression("Error dropping database");
CALL mtr.add_suppression("Can't drop database '.*'; database doesn't exist");
CALL mtr.add_suppression("Slave SQL for channel '': ... The slave coordinator and worker threads are stopped, possibly leaving data in inconsistent state. .* Error_code: 1756");
==== Case 1: CALL is split on master ====
---- Initialize ----
CREATE TABLE t (a INT);
CREATE...

I believe tag binlog-encryption should be removed, because crash happens without any encryption.

Is this upstream?

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1123