BUG#21053526 (Post-push fix for the test case.)

Post-push fix. Fixing the test case binlog_xa_handling,
making it more robust.

Clean up the binlog (RESET MASTER) before running this
particular test case (since it iterates over the log to
find the correct event). Otherwise, it might take too
long or exhaust the loop_count and bail out with a
(false positive) failure.

Author: Luis Soares

mysql-test/suite/binlog/r/binlog_xa_handling.result

@@ -8,10 +8,12 @@ XA END'';
 XA PREPARE'';
 XA COMMIT'';
 DROP TABLE t1;
+RESET MASTER;
 CREATE TABLE t1 (c1 INT);
 XA BEGIN 'xa1';
 INSERT INTO t1 VALUES (1);
 XA END 'xa1';
 XA COMMIT 'xa1' ONE PHASE;
 [Validate that SHOW BINLOG EVENTS shows the ONE PHASE statement.]
 DROP TABLE t1;
+RESET MASTER;

mysql-test/suite/binlog/t/binlog_xa_handling.test

@@ -37,6 +37,11 @@ DROP TABLE t1;
 # mysql-test/extra/binlog_tests/binlog_xa_prepared.test
 #
 
+# clean up binary log so that the following operation
+# does not have to scan through a long history of
+# events in the log (potentially causing a failure).
+RESET MASTER;
+
 CREATE TABLE t1 (c1 INT);
 XA BEGIN 'xa1';
 INSERT INTO t1 VALUES (1);
@@ -48,3 +53,7 @@ XA COMMIT 'xa1' ONE PHASE;
 --source include/wait_for_binlog_event.inc
 
 DROP TABLE t1;
+
+# clean up the binary log at in the end of the test
+# case as well.
+RESET MASTER;