Bug #73304 innodb_zip.innodb_wl6501_1 failing on PB2.
Submitted: 17 Jul 2014 6:48 Modified: 12 Aug 2014 18:52
Reporter: Tarique Saleem Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.7 OS:Any
Assigned to: CPU Architecture:Any

[17 Jul 2014 6:48] Tarique Saleem 
Description:
innodb_zip.innodb_wl6501_1 is failing on daily-trunk and mysql-trunk

http://pb2.no.oracle.com/?template=mysql_show_test_failure&test_failure_id=5517447
http://pb2.no.oracle.com/?template=mysql_show_test_failure&test_failure_id=5512856

innodb_zip.innodb_wl6501_1               w6 [ fail ]  Found warnings/errors in server log file!
        Test ended at 2014-07-06 19:58:07
line
2014-07-06T17:56:08.583806Z 0 [ERROR] InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 98796947 and the end 98797155.
2014-07-06T17:56:13.969825Z 0 [ERROR] InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 98799532 and the end 98799594.
2014-07-06T17:57:56.689744Z 0 [ERROR] InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 99931491 and the end 99931553.
2014-07-06T17:58:03.366387Z 0 [ERROR] InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 99934076 and the end 99934138.
^ Found warnings in /tmp/mtr-16268/var-normal-debug-big/6/log/mysqld.1.err
ok

 - saving '/tmp/mtr-16268/var-normal-debug-big/6/log/innodb_zip.innodb_wl6501_1/' to '/tmp/mtr-16268/var-normal-debug-big/log/innodb_zip.innodb_wl6501_1/'

How to repeat:

Its reproducible on solaris with command, 

./mtr --debug-server --big-test innodb_wl6501_1

Used binary from : http://trollheim.no.oracle.com/archive/12649975.mysql-advanced-5.7.5-m15-solaris11-sparc-6...

Please have a look.
[17 Jul 2014 8:43] Tarique Saleem 
Posted by developer:
 
Similar failure seen with test innodb_zip.innodb_wl6501_debug
[12 Aug 2014 18:52] Daniel Price 
Fixed as of the upcoming 5.7.5 release, and here's the changelog entry:

 An "MLOG_CHECKPOINT" marker was incorrectly omitted when performing a log
checkpoint. 

Thank you for the bug report.