[MDEV-10428] main.information_schema_stats fails sporadically in buildbot Created: 2016-07-24  Updated: 2016-07-24  Resolved: 2016-07-24

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.0, 10.1
Fix Version/s: 10.1.17, 10.0.27

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Elena Stepanova
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
blocks MDEV-7069 Fix buildbot failures in main server ... Stalled

 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/5589/steps/test_7/logs/stdio

CURRENT_TEST: main.information_schema_stats
--- /mnt/buildbot/build/mariadb-10.0.27/mysql-test/r/information_schema_stats.result	2016-07-18 11:08:49.000000000 +0300
+++ /mnt/buildbot/build/mariadb-10.0.27/mysql-test/r/information_schema_stats.reject	2016-07-18 18:46:56.000000000 +0300
@@ -16,8 +16,8 @@
 2
 select * from information_schema.index_statistics where table_schema='test' and table_name='just_a_test';
 TABLE_SCHEMA	TABLE_NAME	INDEX_NAME	ROWS_READ
-test	just_a_test	IND_just_a_test_state	2
 test	just_a_test	IND_just_a_test_first_name_last_name	1
+test	just_a_test	IND_just_a_test_state	2
 select * from information_schema.table_statistics where table_schema='test' and table_name='just_a_test';
 TABLE_SCHEMA	TABLE_NAME	ROWS_READ	ROWS_CHANGED	ROWS_CHANGED_X_INDEXES
 test	just_a_test	18	5	5
@@ -57,8 +57,8 @@
 select * from information_schema.index_statistics where table_schema='test' and table_name='just_a_test';
 TABLE_SCHEMA	TABLE_NAME	INDEX_NAME	ROWS_READ
 test	just_a_test	first_name	1
-test	just_a_test	state	2
 test	just_a_test	PRIMARY	5
+test	just_a_test	state	2
 select * from information_schema.table_statistics where table_schema='test' and table_name='just_a_test';
 TABLE_SCHEMA	TABLE_NAME	ROWS_READ	ROWS_CHANGED	ROWS_CHANGED_X_INDEXES
 test	just_a_test	8	5	15

Result sets need to be sorted



 Comments   
Comment by Elena Stepanova [ 2016-07-24 ]

https://github.com/MariaDB/server/commit/df4fddb8961355fc68f32375d2bac5735057f205

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