[MDEV-8511] tokudb_bugs.db397_update_trigger failed in buildbot Created: 2015-07-21  Updated: 2019-01-22  Resolved: 2019-01-22

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.0
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-7069 Fix buildbot failures in main server ... Stalled

 Description   

Happened once so far
http://buildbot.askmonty.org/buildbot/builders/bld-dan-release/builds/2621/steps/test/logs/stdio

tokudb_bugs.db397_update_trigger         w2 [ fail ]
        Test ended at 2015-07-20 10:33:24
 
CURRENT_TEST: tokudb_bugs.db397_update_trigger
--- /opt/buildbot-slave/mariadb/dan_demeter2/build/storage/tokudb/mysql-test/tokudb_bugs/r/db397_update_trigger.result	2015-07-09 03:54:46.820958474 +0300
+++ /opt/buildbot-slave/mariadb/dan_demeter2/build/storage/tokudb/mysql-test/tokudb_bugs/r/db397_update_trigger.reject	2015-07-20 10:33:24.116049513 +0300
@@ -27,9 +27,9 @@
 1	BEFORE UPDATE
 select locks_dname,locks_key_left,locks_key_right from information_schema.tokudb_locks;
 locks_dname	locks_key_left	locks_key_right
-./test/t1_audit-main	0200000000000000	0200000000000000
 ./test/t1-main	ff01000000	0101000000
 ./test/t1-main	0001000000	0001000000
+./test/t1_audit-main	0200000000000000	0200000000000000
 commit;
 drop trigger t1_trigger;
 create trigger t1_trigger after update on t1
@@ -50,9 +50,9 @@
 2	AFTER UPDATE
 select locks_dname,locks_key_left,locks_key_right from information_schema.tokudb_locks;
 locks_dname	locks_key_left	locks_key_right
-./test/t1_audit-main	0300000000000000	0300000000000000
 ./test/t1-main	ff02000000	0102000000
 ./test/t1-main	0002000000	0002000000
+./test/t1_audit-main	0300000000000000	0300000000000000
 commit;
 drop trigger t1_trigger;
 drop table t1, t1_audit;
 
mysqltest: Result content mismatch



 Comments   
Comment by Elena Stepanova [ 2019-01-22 ]

Last time seen in 2016, and even if it's still there, it's not going to be fixed. Closing.

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