[MDEV-33421] innodb.corrupted_during_recovery fails due to error that the table is corrupted Created: 2024-02-07  Updated: 2024-02-08

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - InnoDB, Tests
Affects Version/s: 10.11, 11.0, 11.1, 11.2, 11.3, 11.4
Fix Version/s: 10.11, 11.0, 11.1, 11.2, 11.3, 11.4

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


 Description   

The test innodb.corrupted_during_recovery is occasionally failing like this, mostly on MSAN or the Valgrind builder, but also some others:

10.11 f30244d13cff7fe3270216ef2214d3463305a0a9

 
innodb.corrupted_during_recovery 'innodb' w35 [ fail ]  Found warnings/errors in server log file!
 
        Test ended at 2024-02-07 08:14:36
 
line
 
2024-02-07  8:14:18 3 [ERROR] InnoDB: Table `test`.`t1` is corrupted. Please drop the table and recreate.
 
^ Found warnings in /buildbot/amd64-ubuntu-2204-valgrind/build/mysql-test/var/35/log/mysqld.1.err

I think that we simply need to add a suppression for this rare error. Even though I did not find any failures of this type in the 10.6 branch, I think that we’d better add the suppression already there, just in case.

 Comments   
Comment by Marko Mäkelä [ 2024-02-07 ]

The suppression was added in MDEV-19541 and it exists in the 10.6 branch, which is why the test does not fail in 10.6 or earlier. The suppression was lost in an incorrect merge from 10.6 to 10.7.

Generated at Thu Feb 08 10:38:47 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.