[MDEV-20149] innodb.innodb-system-table-view failed in buildbot with wrong result Created: 2019-07-24  Updated: 2019-08-29  Resolved: 2019-08-29

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.3
Fix Version/s: 10.3.18, 10.4.8

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Marko Mäkelä
Resolution: Fixed Votes: 1
Labels: None


 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/18699

10.3 559584fd9a5e9785e58940f11df02160

nnodb.innodb-system-table-view '8k,innodb' w4 [ fail ]
        Test ended at 2019-07-22 05:50:46
 
CURRENT_TEST: innodb.innodb-system-table-view
Warning: /mnt/buildbot/build/mariadb-10.3.17/libmysqld/examples/mysqltest_embedded: unknown variable 'loose-ssl-ca=/mnt/buildbot/build/mariadb-10.3.17/mysql-test/std_data/cacert.pem'
Warning: /mnt/buildbot/build/mariadb-10.3.17/libmysqld/examples/mysqltest_embedded: unknown variable 'loose-ssl-cert=/mnt/buildbot/build/mariadb-10.3.17/mysql-test/std_data/client-cert.pem'
Warning: /mnt/buildbot/build/mariadb-10.3.17/libmysqld/examples/mysqltest_embedded: unknown variable 'loose-ssl-key=/mnt/buildbot/build/mariadb-10.3.17/mysql-test/std_data/client-key.pem'
Warning: /mnt/buildbot/build/mariadb-10.3.17/libmysqld/examples/mysqltest_embedded: unknown option '--loose-skip-ssl'
--- /mnt/buildbot/build/mariadb-10.3.17/mysql-test/suite/innodb/r/innodb-system-table-view.result	2019-07-22 05:17:12.000000000 -0400
+++ /mnt/buildbot/build/mariadb-10.3.17/mysql-test/suite/innodb/r/innodb-system-table-view.reject	2019-07-22 05:50:44.814617546 -0400
@@ -112,7 +112,7 @@
 FROM INFORMATION_SCHEMA.INNODB_SYS_TABLESTATS
 WHERE name LIKE "%parent";
 name	num_rows	ref_count
-test/parent	1	1
+test/parent	1	2
 SELECT NAME, FLAG, N_COLS FROM INFORMATION_SCHEMA.INNODB_SYS_TABLES
 WHERE name NOT LIKE 'sys/%';
 NAME	FLAG	N_COLS
 
mysqltest: Result content mismatch



 Comments   
Comment by Marko Mäkelä [ 2019-08-29 ]

The test failed in 10.3+ due to MDEV-12288 causing purge activity after INSERT. The fix was to use wait_all_purged.inc.

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