[MDEV-24057] binlog.binlog_stm_mix_innodb_myisam failed in buildbot with wrong result Created: 2020-10-29  Updated: 2023-11-29  Resolved: 2023-11-29

Status: Closed
Project: MariaDB Server
Component/s: Replication, Tests
Affects Version/s: 10.1
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

http://buildbot.askmonty.org/buildbot/builders/mac-1012-bintar/builds/7706/steps/test/logs/stdio

binlog.binlog_stm_mix_innodb_myisam 'innodb_plugin,stmt' [ fail ]
        Test ended at 2020-08-12 06:10:57
 
CURRENT_TEST: binlog.binlog_stm_mix_innodb_myisam
--- /Users/buildbot/maria-slave/mac-1012-bintar/build/mysql-test/suite/binlog/r/binlog_stm_mix_innodb_myisam.result	2020-08-11 23:48:33.000000000 -0400
+++ /Users/buildbot/maria-slave/mac-1012-bintar/build/mysql-test/suite/binlog/r/binlog_stm_mix_innodb_myisam.reject	2020-08-12 06:10:56.000000000 -0400
@@ -98,7 +98,7 @@
 Note	1592	Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.
 select get_lock("a",10);
 get_lock("a",10)
-1
+0
 include/show_binlog_events.inc
 Log_name	Pos	Event_type	Server_id	End_log_pos	Info
 master-bin.000001	#	Gtid	#	#	BEGIN GTID #-#-#
 
mysqltest: Result content mismatch


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