[MDEV-25363] binlog_stm_datetime_ranges_mdev15289 fails when is preceded by a certain test Created: 2021-04-07  Updated: 2021-04-14  Resolved: 2021-04-14

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.3, 10.4, 10.5
Fix Version/s: 10.2.38, 10.3.29, 10.4.19, 10.5.10

Type: Bug Priority: Major
Reporter: Andrei Elkin Assignee: Alice Sherepa
Resolution: Fixed Votes: 0
Labels: None


 Description   

The test fails when invoked after

binlog.binlog_statement_insert_delayed

with the following trace

CURRENT_TEST: binlog.binlog_stm_datetime_ranges_mdev15289
--- /home/andrei/MDB.WTs.Review/Review_4/mysql-test/suite/binlog/r/binlog_stm_datetime_ranges_mdev15289.result	2020-09-25 20:08:01.000000000 +0300
+++ /home/andrei/MDB.WTs.Review/Review_4/mysql-test/suite/binlog/r/binlog_stm_datetime_ranges_mdev15289.reject	2021-04-07 20:26:09.940631971 +0300
@@ -1,5 +1,17 @@
 include/show_binlog_events.inc
 Log_name	Pos	Event_type	Server_id	End_log_pos	Info
+master-bin.000001	#	Gtid	#	#	BEGIN GTID #-#-#
+master-bin.000001	#	Intvar	#	#	INSERT_ID=301
+master-bin.000001	#	Query	#	#	use `test`; insert /* before delayed */  /* after delayed */ into t1 values (null),(null),(null),(null)
+master-bin.000001	#	Query	#	#	COMMIT
+master-bin.000001	#	Gtid	#	#	BEGIN GTID #-#-#
+master-bin.000001	#	Intvar	#	#	INSERT_ID=305
+master-bin.000001	#	Query	#	#	use `test`; insert  /*! 

which hints at binlog.binlog_statement_insert_delayed having not done a proper cleanup.



 Comments   
Comment by Alice Sherepa [ 2021-04-14 ]

fixed by 7b791b82b86ced825a2cc

Generated at Thu Feb 08 09:37:07 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.