BUG#32008512 ASSERTION `LOST_GTIDS->IS_EMPTY()' FAILED WHEN MYSQLD STARTED

Pedro Figueiredo · surbhat1595 · commit 15ae11876f77 · 2021-03-22T13:09:14.000+01:00
BUG#32134875 PURGE BINLOG IN INSTANCE STARTUP CAUSE PREVIOUS_GTIDS WRONG IN NEW BINLOG FILE

[post-push]

Analysis/Fix
------------
Missing include in test script to prevent test from running in non-debug
mode.

Reviewed-by: Sven Sandberg &lt;sven.sandberg@oracle.com&gt;

(cherry picked from commit 586d92acb166c323a89a89c5edaefd047dc01347)
diff --git a/mysql-test/suite/binlog/t/binlog_gtid_purge_binlog_at_startup.test b/mysql-test/suite/binlog/t/binlog_gtid_purge_binlog_at_startup.test
@@ -42,6 +42,7 @@
 #
 --source include/have_binlog_format_row.inc
 --source include/have_gtid.inc
+--source include/have_debug.inc
 
 --let $saved_debug = `SELECT @@debug`
 

Original file line number	Diff line number	Diff line change
`@@ -42,6 +42,7 @@`
`42`	`42`	`#`
`43`	`43`	`--source include/have_binlog_format_row.inc`
`44`	`44`	`--source include/have_gtid.inc`
	`45`	`+--source include/have_debug.inc`
`45`	`46`
`46`	`47`	--let $saved_debug = `SELECT @@debug`
`47`	`48`