[MDEV-13251] innodb.log_corruption failed in buildbot Created: 2017-07-06  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: Minor
Reporter: Elena Stepanova Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-trusty-x86/builds/1579/steps/test/logs/stdio

innodb.log_corruption 'innodb'           w4 [ fail ]
        Test ended at 2017-06-16 18:36:20
 
CURRENT_TEST: innodb.log_corruption
--- /usr/local/mariadb-10.2.7-linux-i686/mysql-test/suite/innodb/r/log_corruption.result	2017-06-16 17:14:38.000000000 +0000
+++ /usr/local/mariadb-10.2.7-linux-i686/mysql-test/suite/innodb/r/log_corruption.reject	2017-06-16 18:36:20.532785821 +0000
@@ -85,7 +85,7 @@
 AND support IN ('YES', 'DEFAULT', 'ENABLED');
 ENGINE	SUPPORT	COMMENT	TRANSACTIONS	XA	SAVEPOINTS
 FOUND 1 /InnoDB: MLOG_FILE_NAME incorrect:bigot/ in mysqld.1.err
-FOUND 1 /len 22; hex 38000000000012860cb7809781e800066269676f7400; asc 8               bigot ;/ in mysqld.1.err
+NOT FOUND /len 22; hex 38000000000012860cb7809781e800066269676f7400; asc 8               bigot ;/ in mysqld.1.err
 # missing MLOG_FILE_NAME or MLOG_FILE_DELETE before MLOG_CHECKPOINT
 SELECT * FROM INFORMATION_SCHEMA.ENGINES
 WHERE engine = 'innodb'
 
mysqltest: Result length mismatch



 Comments   
Comment by Marko Mäkelä [ 2018-11-20 ]

The logs are no longer available, but I wonder if this could be caused by some interleaved output in the error log.
That said, this was filed after MDEV-11027 was fixed, and I don't think that this test could possibly exercise the code that was later modified in MDEV-12323.

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