[MDEV-15681] innodb.purge_secondary fails in buildbot with wrong result Created: 2018-03-26  Updated: 2023-11-29  Resolved: 2023-11-29

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.2
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/12052/steps/mtr_nm/logs/stdio

innodb.purge_secondary 'innodb'          w3 [ fail ]
        Test ended at 2018-03-26 15:26:19
 
CURRENT_TEST: innodb.purge_secondary
--- /mnt/buildbot/build/mariadb-10.2.14/mysql-test/suite/innodb/r/purge_secondary.result	2018-03-26 13:44:58.000000000 +0300
+++ /mnt/buildbot/build/mariadb-10.2.14/mysql-test/suite/innodb/r/purge_secondary.reject	2018-03-26 15:26:19.000000000 +0300
@@ -158,7 +158,6 @@
 SELECT NAME, SUBSYSTEM FROM INFORMATION_SCHEMA.INNODB_METRICS
 WHERE NAME="buffer_LRU_batch_evict_total_pages" AND COUNT > 0;
 NAME	SUBSYSTEM
-buffer_LRU_batch_evict_total_pages	buffer
 # Note: The OTHER_INDEX_SIZE does not cover any SPATIAL INDEX.
 # To test that all indexes were emptied, replace DROP TABLE
 # with the following, and examine the root pages in t1.ibd:
 
mysqltest: Result length mismatch


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