Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
10.0(EOL), 10.1(EOL), 10.2(EOL)
-
10.2.1-5
Description
http://buildbot.askmonty.org/buildbot/builders/bintar-rhel7-p8/builds/16/steps/test/logs/stdio
main.index_merge_innodb 'xtradb' w1 [ fail ]
|
Test ended at 2014-11-19 12:27:44
|
 |
CURRENT_TEST: main.index_merge_innodb
|
--- /home/buildbot/maria-slave/power8-vlp03-bintar/build/mysql-test/r/index_merge_innodb.result 2014-11-19 10:43:11.911410000 -0500
|
+++ /home/buildbot/maria-slave/power8-vlp03-bintar/build/mysql-test/r/index_merge_innodb.reject 2014-11-19 12:27:43.950083391 -0500
|
@@ -313,7 +313,7 @@
|
update t1 set key2=key1,key3=key1;
|
explain select * from t1 where (key3 > 30 and key3<35) or (key2 >32 and key2 < 40);
|
id select_type table type possible_keys key key_len ref rows Extra
|
-1 SIMPLE t1 index_merge i2,i3 i3,i2 4,4 NULL REF Using sort_union(i3,i2); Using where
|
+1 SIMPLE t1 ALL i2,i3 NULL NULL NULL REF Using where
|
select * from t1 where (key3 > 30 and key3<35) or (key2 >32 and key2 < 40);
|
key1 key2 key3
|
31 31 31
|
It happens from time to time on different builds.
Attachments
Issue Links
- relates to
-
MDEV-7069 Fix buildbot failures in main server trees
- Stalled
-
MDEV-14121 Assertion failure 'slot != NULL' in os_aio_linux_collect() during main.index_merge_innodb
- Closed
-
MDEV-15203 innodb.innodb_max_recordsize_64k failed in buildbot with wrong result
- Closed