[MDEV-17284] rocksdb.dup_key_update failed in buildbot with wrong result Created: 2018-09-24  Updated: 2023-11-29  Resolved: 2023-11-29

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - RocksDB, Tests
Affects Version/s: 10.2
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Sergei Petrunia
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-deb-trusty-amd64/builds/12118

rocksdb.dup_key_update 'write_committed' w1 [ fail ]
        Test ended at 2018-09-13 23:06:17
 
CURRENT_TEST: rocksdb.dup_key_update
--- /usr/share/mysql/mysql-test/plugin/rocksdb/rocksdb/r/dup_key_update.result	2018-09-13 18:47:26.000000000 +0000
+++ /run/shm/var/1/log/dup_key_update.reject	2018-09-13 23:06:16.906355668 +0000
@@ -294,10 +294,12 @@
 INSERT INTO t2 VALUES (1, 1, 1) ON DUPLICATE KEY UPDATE id2 = 11;
 SELECT * FROM t2 WHERE id1 = 1;
 id1	id2	id3
-1	11	1
+1	1	1
+1	10	1
 SELECT * FROM t2 FORCE INDEX (id3) WHERE id3 = 1;
 id1	id2	id3
-1	11	1
+1	1	1
+1	10	1
 INSERT INTO t2 VALUES (5, 5, 5) ON DUPLICATE KEY UPDATE id2 = 12;
 SELECT * FROM t2 WHERE id1 = 5;
 id1	id2	id3
@@ -342,7 +344,8 @@
 9	17	9
 SELECT * FROM t2;
 id1	id2	id3
-1	11	1
+1	1	1
+1	10	1
 2	2	2
 3	3	3
 4	4	4
@@ -353,7 +356,8 @@
 9	17	9
 SELECT * FROM t2 FORCE INDEX (id3);
 id1	id2	id3
-1	11	1
+1	1	1
+1	10	1
 2	2	2
 3	3	3
 4	4	4
 
mysqltest: Result length mismatch



 Comments   
Comment by Sergei Petrunia [ 2018-10-09 ]

The only time this testcase has failed was on 2018-09-14, which was the cause of this report.
No other failures like that since July 2018 until today (Oct, 9)

Generated at Thu Feb 08 08:35:18 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.