Test binlog.binlog_gtid_state_update_deadlock is failing on 5.7 trunk

The test case binlog.binlog_gtid_state_update_deadlock is failing on 5.7 trunk.

17:13:34 binlog.binlog_gtid_state_update_deadlock 'stmt' w3 [ pass ] 600158
17:13:34
17:13:34 MTR's internal check of the test case 'binlog.binlog_gtid_state_update_deadlock' failed.
17:13:34 This means that the test case does not preserve the state that existed
17:13:34 before the test case was executed. Most likely the test case did not
17:13:34 do a proper clean-up. It could also be caused by the previous test run
17:13:34 by this thread, if the server wasn't restarted.
17:13:34 This is the diff of the states of the servers before and after the
17:13:34 test case was executed:
17:13:34 mysqltest: Logging to '/mnt/workspace/percona-server-5.7-trunk/BUILD_TYPE/debug/Host/centos7-64/build/mysql-test/var/3/tmp/check-mysqld_1.log'.
17:13:34 mysqltest: Results saved in '/mnt/workspace/percona-server-5.7-trunk/BUILD_TYPE/debug/Host/centos7-64/build/mysql-test/var/3/tmp/check-mysqld_1.result'.
17:13:34 mysqltest: Connecting to server localhost:13011 (socket /tmp/GsD61S5_8z/3/mysqld.1.sock) as 'root', connection 'default', attempt 0 ...
17:13:34 mysqltest: ... Connected.
17:13:34 mysqltest: Start processing test commands from './include/check-testcase.test' ...
17:13:34 mysqltest: ... Done processing test commands.
17:13:34 --- /mnt/workspace/percona-server-5.7-trunk/BUILD_TYPE/debug/Host/centos7-64/build/mysql-test/var/3/tmp/check-mysqld_1.result 2017-05-03 20:03:30.390000000 +0300
17:13:34 +++ /mnt/workspace/percona-server-5.7-trunk/BUILD_TYPE/debug/Host/centos7-64/build/mysql-test/var/3/tmp/check-mysqld_1.reject 2017-05-03 20:13:32.006000000 +0300
17:13:34 @@ -668,7 +668,7 @@
17:13:34 VERSION_COMPILE_OS Linux
17:13:34 WAIT_TIMEOUT 28800
17:13:34 VARIABLE_NAME VARIABLE_VALUE
17:13:34 -DEBUG_SYNC ON - signals: ''
17:13:34 +DEBUG_SYNC ON - signals: 'have_gtid_mode_lock'