[MDEV-24024] innodb.ibuf_not_empty failed in buildbot Created: 2020-10-26  Updated: 2020-10-27  Resolved: 2020-10-27

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.5
Fix Version/s: 10.5.7

Type: Bug Priority: Major
Reporter: Alice Sherepa Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-19021 innodb.ibuf_not_empty failed in build... Closed
relates to MDEV-23399 10.5 performance regression with IO-b... Closed

 Description   

http://buildbot.askmonty.org/buildbot/builders/winx64-debug/builds/21598/steps/test/logs/stdio

innodb.ibuf_not_empty 'innodb,strict_crc32' w4 [ fail ]
        Test ended at 2020-10-24 09:56:28
 
CURRENT_TEST: innodb.ibuf_not_empty
--- D:/winx64-debug/build/src/mysql-test/suite/innodb/r/ibuf_not_empty.result	2020-10-24 09:40:27.610487900 +0000
+++ D:\winx64-debug\build\src\mysql-test\suite\innodb\r\ibuf_not_empty.reject	2020-10-24 09:56:28.715051700 +0000
@@ -9,7 +9,7 @@
 # restart: --innodb-force-recovery=6 --innodb-change-buffer-dump
 check table t1;
 Table	Op	Msg_type	Msg_text
-test.t1	check	Warning	InnoDB: Index 'b' contains 990 entries, should be 1024.
+test.t1	check	Warning	InnoDB: Index 'b' contains 991 entries, should be 1024.
 test.t1	check	error	Corrupt
 # restart
 SET GLOBAL innodb_fast_shutdown=0;
 
mysqltest: Result content mismatch



 Comments   
Comment by Marko Mäkelä [ 2020-10-27 ]

MDEV-23399 changed the operation of the page cleaner thread. I would tend to blame this test failure on those changes.

Comment by Marko Mäkelä [ 2020-10-27 ]

I relaxed the test so that any amount will be mapped to 990 in the output of that CHECK TABLE command.

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