[MDEV-16946] innodb.alter_kill failed in buildbot with wrong result Created: 2018-08-11  Updated: 2018-10-10  Resolved: 2018-10-10

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB, Tests
Affects Version/s: 10.2
Fix Version/s: 10.3.11, 10.2.19

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


 Description   

http://buildbot.askmonty.org/buildbot/builders/win32-packages/builds/9251

innodb.alter_kill 'innodb'               w1 [ fail ]
 
        Test ended at 2018-08-03 06:41:41
 
 
 
CURRENT_TEST: innodb.alter_kill
 
--- D:/win32-packages/build/src/mysql-test/suite/innodb/r/alter_kill.result	2018-08-03 05:45:07.000000000 +0000
 
+++ D:\win32-packages\build\src\mysql-test\suite\innodb\r\alter_kill.reject	2018-08-03 06:41:25.977718200 +0000
 
@@ -62,7 +62,7 @@
 
 # Kill the server
 
 disconnect con1;
 
 # Attempt to start without an *.ibd file.
 
-FOUND 1 /\[ERROR\] InnoDB: Tablespace [0-9]+ was not found at .*test.bug16735660.ibd/ in mysqld.1.err
 
+NOT FOUND /\[ERROR\] InnoDB: Tablespace [0-9]+ was not found at .*test.bug16735660.ibd/ in mysqld.1.err
 
 SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
 
 SELECT * FROM bug16735660;
 
 a
 
 
 
mysqltest: Result length mismatch



 Comments   
Comment by Marko Mäkelä [ 2018-10-10 ]

The failure was caused by a redo log checkpoint that occurred at a critical moment before the kill-and-restart. I was able to reproduce the failure by adding

SET GLOBAL innodb_log_checkpoint_now=ON;

immediately before the kill. (The parameter is only available in debug builds.)

I fixed it so that the test will be skipped if a log checkpoint occurs at the critical moment.

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