[MDEV-20538] main.rowid_filter_innodb failed in buildbot with wrong result Created: 2019-09-08  Updated: 2023-12-05

Status: Stalled
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.4, 10.5
Fix Version/s: 10.4, 10.5

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Sergei Petrunia
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Duplicate

 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest/builds/19924

10.4 c1a2778e689030fcbb6cdc93d8c1f1d8

main.rowid_filter_innodb 'innodb'        w2 [ fail ]
        Test ended at 2019-09-07 05:41:19
 
CURRENT_TEST: main.rowid_filter_innodb
--- /mnt/buildbot/build/mariadb-10.4.8/mysql-test/main/rowid_filter_innodb.result	2019-09-07 03:37:56.000000000 -0400
+++ /mnt/buildbot/build/mariadb-10.4.8/mysql-test/main/rowid_filter_innodb.reject	2019-09-07 05:41:19.377566069 -0400
@@ -1634,7 +1634,7 @@
       "key_length": "9",
       "used_key_parts": ["o_totaldiscount"],
       "rows": 41,
-      "filtered": 2.0711,
+      "filtered": 2.0467,
       "index_condition": "orders.o_totaldiscount between 18000 and 20000",
       "attached_condition": "orders.o_totalprice between 200000 and 220000 and orders.o_orderDATE between '1992-12-01' and '1997-01-01'"
     },
@@ -1664,7 +1664,7 @@
 o_totalprice BETWEEN 200000 AND 220000 AND
 l_shipdate BETWEEN '1996-10-01' AND '1996-12-01';
 id	select_type	table	type	possible_keys	key	key_len	ref	rows	r_rows	filtered	r_filtered	Extra
-1	SIMPLE	orders	range	PRIMARY,i_o_orderdate,i_o_totalprice,i_o_totaldiscount	i_o_totaldiscount	9	NULL	41	41.00	2.07	2.44	Using index condition; Using where
+1	SIMPLE	orders	range	PRIMARY,i_o_orderdate,i_o_totalprice,i_o_totaldiscount	i_o_totaldiscount	9	NULL	41	41.00	2.05	2.44	Using index condition; Using where
 1	SIMPLE	lineitem	ref	PRIMARY,i_l_shipdate,i_l_orderkey,i_l_orderkey_quantity	PRIMARY	4	dbt3_s001.orders.o_orderkey	4	6.00	3.05	66.67	Using where
 set statement optimizer_switch='rowid_filter=on' for ANALYZE FORMAT=JSON SELECT o_totaldiscount, o_totalprice, l_shipdate
 FROM v1, lineitem
@@ -1694,7 +1694,7 @@
       "rows": 41,
       "r_rows": 41,
       "r_total_time_ms": "REPLACED",
-      "filtered": 2.0711,
+      "filtered": 2.0467,
       "r_filtered": 2.439,
       "index_condition": "orders.o_totaldiscount between 18000 and 20000",
       "attached_condition": "orders.o_totalprice between 200000 and 220000 and orders.o_orderDATE between '1992-12-01' and '1997-01-01'"
@@ -1765,7 +1765,7 @@
       "key_length": "9",
       "used_key_parts": ["o_totaldiscount"],
       "rows": 41,
-      "filtered": 2.0711,
+      "filtered": 2.0467,
       "index_condition": "orders.o_totaldiscount between 18000 and 20000",
       "attached_condition": "orders.o_totalprice between 200000 and 220000 and orders.o_orderDATE between '1992-12-01' and '1997-01-01'"
     },
@@ -1795,7 +1795,7 @@
 o_totalprice BETWEEN 200000 AND 220000 AND
 l_shipdate BETWEEN '1996-10-01' AND '1996-12-01';
 id	select_type	table	type	possible_keys	key	key_len	ref	rows	r_rows	filtered	r_filtered	Extra
-1	SIMPLE	orders	range	PRIMARY,i_o_orderdate,i_o_totalprice,i_o_totaldiscount	i_o_totaldiscount	9	NULL	41	41.00	2.07	2.44	Using index condition; Using where
+1	SIMPLE	orders	range	PRIMARY,i_o_orderdate,i_o_totalprice,i_o_totaldiscount	i_o_totaldiscount	9	NULL	41	41.00	2.05	2.44	Using index condition; Using where
 1	SIMPLE	lineitem	ref	PRIMARY,i_l_shipdate,i_l_orderkey,i_l_orderkey_quantity	PRIMARY	4	dbt3_s001.orders.o_orderkey	4	6.00	3.05	66.67	Using where
 set statement optimizer_switch='rowid_filter=off' for ANALYZE FORMAT=JSON SELECT o_totaldiscount, o_totalprice, l_shipdate
 FROM v1, lineitem
@@ -1825,7 +1825,7 @@
       "rows": 41,
       "r_rows": 41,
       "r_total_time_ms": "REPLACED",
-      "filtered": 2.0711,
+      "filtered": 2.0467,
       "r_filtered": 2.439,
       "index_condition": "orders.o_totaldiscount between 18000 and 20000",
       "attached_condition": "orders.o_totalprice between 200000 and 220000 and orders.o_orderDATE between '1992-12-01' and '1997-01-01'"
 
mysqltest: Result content mismatch



 Comments   
Comment by Alice Sherepa [ 2020-09-01 ]

on 10.5 (31e6c96b0449761dc15f54)
http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest/builds/25370/steps/mtr_ps/logs/stdio

main.rowid_filter_innodb 'innodb'        w4 [ fail ]
        Test ended at 2020-08-31 05:39:03
 
CURRENT_TEST: main.rowid_filter_innodb
--- /mnt/buildbot/build/mariadb-10.5.6/mysql-test/main/rowid_filter_innodb.result	2020-08-31 03:57:38.000000000 -0400
+++ /mnt/buildbot/build/mariadb-10.5.6/mysql-test/main/rowid_filter_innodb.reject	2020-08-31 05:39:03.103494822 -0400
@@ -2119,7 +2119,7 @@
 select * from t1
 where el_index like '10%' and (el_index_60 like '10%' or el_index_60 like '20%');
 id	select_type	table	type	possible_keys	key	key_len	ref	rows	Extra
-1	SIMPLE	t1	range	el_index,el_index_60	el_index	62	NULL	1000	Using where
+1	SIMPLE	t1	ALL	el_index,el_index_60	NULL	NULL	NULL	4846	Using where
 drop table t10, t11, t1;
 #
 # MDEV-22160: SIGSEGV in st_join_table::save_explain_data on SELECT
 
mysqltest: Result length mismatch

Comment by Varun Gupta (Inactive) [ 2020-09-21 ]

the fix in the above comment by Alice should be fixed by the patch

commit b795adcff72a84421576748646e2446e3ef24202
Author: Sergei Petrunia <psergey@askmonty.org>
Date:   Thu Sep 3 15:37:04 2020 +0300
 
    Make rowid_filter_innodb test stable
    
    It was failing on mac-1012-bintar.

Comment by Julien Fritsch [ 2023-12-05 ]

Automated message:
----------------------------
Since this issue has not been updated since 6 weeks, it's time to move it back to Stalled.

Comment by JiraAutomate [ 2023-12-05 ]

Automated message:
----------------------------
Since this issue has not been updated since 6 weeks, it's time to move it back to Stalled.

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