MDEV-15393 post push trying to understand [ fail ] of the new test

mysql-test/suite/rpl/r/rpl_mysqldump_gtid_slave_pos.result

@@ -30,10 +30,13 @@ insert into t1 set a = 4;
 insert into t1 set a = 3;
 insert into t1 set a = 2;
 insert into t1 set a = 1;
-include/save_master_gtid.inc
 connection slave;
 include/start_slave.inc
-include/sync_with_master_gtid.inc
+connection master;
+connection slave;
+select @@global.gtid_slave_pos as "after initial inserts";
+after initial inserts
+0-1-6
 select * from mysql.gtid_slave_pos;
 domain_id	sub_id	server_id	seq_no
 0	2	1	1

mysql-test/suite/rpl/t/rpl_mysqldump_gtid_slave_pos.test

@@ -44,11 +44,16 @@ while ($i)
   eval insert into t1 set a = $i;
   --dec $i
 }
---source include/save_master_gtid.inc
+###??? --source include/save_master_gtid.inc
 
 --connection slave
 --source include/start_slave.inc
---source include/sync_with_master_gtid.inc
+###??? --source include/sync_with_master_gtid.inc
+
+--connection master
+sync_slave_with_master;
+select @@global.gtid_slave_pos as "after initial inserts";
+
 # Prior tests in a mtr batch could leave the min value of sub_id column with
 # arbtirary value. Therefore before dumping let's
 # adjust mysql.gtid_slave_pos to have sub_id growing deterministically.