[MDEV-15668] innodb.log_file_size failed in buildbot due to not found pattern Created: 2018-03-26  Updated: 2022-02-12  Resolved: 2022-02-11

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB, Tests
Affects Version/s: 10.0, 10.1
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None


 Description   

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

innodb.log_file_size '4k,xtradb'         w4 [ fail ]
        Test ended at 2018-03-15 17:10:18
 
CURRENT_TEST: innodb.log_file_size
--- D:/winx64-debug/build/src/mysql-test/suite/innodb/r/log_file_size.result	2018-03-15 16:33:23.796741400 +0000
+++ D:\winx64-debug\build\src\mysql-test\suite\innodb\r\log_file_size.reject	2018-03-15 17:10:17.836456300 +0000
@@ -28,7 +28,7 @@
 ERROR 42000: Unknown storage engine 'InnoDB'
 SELECT * FROM t1;
 ERROR 42000: Unknown storage engine 'InnoDB'
-FOUND /InnoDB: innodb_read_only prevents crash recovery/ in mysqld.1.err
+NOT FOUND /InnoDB: innodb_read_only prevents crash recovery/ in mysqld.1.err
 SELECT * FROM t1;
 ERROR 42000: Unknown storage engine 'InnoDB'
 FOUND /redo log from 3\*[0-9]+ to 2\*[0-9]+ pages/ in mysqld.1.err
@@ -37,7 +37,7 @@
 FOUND /redo log from 3\*[0-9]+ to 2\*[0-9]+ pages/ in mysqld.1.err
 SELECT * FROM t1;
 ERROR 42000: Unknown storage engine 'InnoDB'
-FOUND /InnoDB: innodb_read_only prevents crash recovery/ in mysqld.1.err
+NOT FOUND /InnoDB: innodb_read_only prevents crash recovery/ in mysqld.1.err
 SELECT * FROM t1;
 ERROR 42000: Unknown storage engine 'InnoDB'
 FOUND /redo log from 3\*[0-9]+ to 2\*[0-9]+ pages/ in mysqld.1.err
 
mysqltest: Result length mismatch



 Comments   
Comment by Elena Stepanova [ 2018-04-26 ]

Also on 10.0 http://buildbot.askmonty.org/buildbot/builders/winx64-debug/builds/7295 (earlier)

Comment by Marko Mäkelä [ 2022-02-11 ]

The latest failures of this form occurred in 2019, on 10.0 or 10.1 based staging branches. The last failures on main branches occurred as follows:

10.0 7e606a2d5ca59dbd901b7c8909214a0f 2018-12-19 06:33:56
10.1 757e3b88d26f8282df83f42ea3c451d2 2018-08-07 15:34:39

mariadb-10.1.48 was released in October/November 2020. 10.1 reached its end of life (EOL) on October 17, 2020, and 10.1 had reached its EOL earlier. It is hard to say whether this was ever truly fixed. But, it looks like 10.2 and later releases were never affected by this.

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