Test main.index_merge_innodb is unstable

Bug #1659746 reported by Laurynas Biveinis on 2017-01-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.5
Invalid
Undecided
Unassigned
5.6
Fix Released
Low
Laurynas Biveinis
5.7
Fix Released
Low
Laurynas Biveinis

Bug Description

On 5.6 trunk:

main.index_merge_innodb w2 [ fail ]
        Test ended at 2017-01-11 08:54:34

CURRENT_TEST: main.index_merge_innodb
--- /mnt/workspace/percona-server-5.6-trunk/BUILD_TYPE/debug/Host/ubuntu-xenial-32bit/mysql-test/r/index_merge_innodb.result 2017-01-03 15:06:26.917177432 +0300
+++ /mnt/workspace/percona-server-5.6-trunk/BUILD_TYPE/debug/Host/ubuntu-xenial-32bit/build/mysql-test/var/2/log/index_merge_innodb.reject 2017-01-11 16:54:33.476707245 +0300
@@ -698,7 +698,7 @@
 key1 key2 filler1
 explain select key1,key2,key3,key4,filler1 from t1 where key1=100 and key2=100 or key3=100 and key4=100;
 id select_type table type possible_keys key key_len ref rows Extra
-1 SIMPLE t1 index_merge key1,key2,key3,key4 key1,key2,key3,key4 5,5,5,5 NULL 4 Using union(intersect(key1,key2),intersect(key3,key4)); Using where
+1 SIMPLE t1 index_merge key1,key2,key3,key4 key1,key2,key4,key3 5,5,5,5 NULL 4 Using union(intersect(key1,key2),intersect(key4,key3)); Using where
 select key1,key2,key3,key4,filler1 from t1 where key1=100 and key2=100 or key3=100 and key4=100;
 key1 key2 key3 key4 filler1
 -1 -1 100 100 key4-key3

mysqltest: Result content mismatch

tags: added: ci upstream

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2226

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers