Percona Server moved to https://jira.percona.com/projects/PS

Make MTR dump server's error log in case warnings found

Bug #1672389 reported by Laurynas Biveinis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.5
Fix Released
Medium
Laurynas Biveinis
Percona Server moved to https://jira.percona.com/projects/PS 5.5.55-38.8
5.6
Fix Released
Medium
Laurynas Biveinis
Percona Server moved to https://jira.percona.com/projects/PS 5.6.36-82.0
5.7
Fix Released
Medium
Laurynas Biveinis
Percona Server moved to https://jira.percona.com/projects/PS 5.7.18-14

Bug Description

Currently, if an MTR warning check is triggered, the full error log context is not necessarily provided, e.g.

innodb.innodb_bug42419 w4 [ fail ] Found warnings/errors in server log file!
        Test ended at 2017-03-10 08:40:09
line
InnoDB: Warning: a long semaphore wait:
.... repeated 9 times: InnoDB: Warning: a long semaphore wait:
^ Found warnings in /mnt/workspace/percona-server-5.6-trunk/BUILD_TYPE/release/Host/centos5-64/build/mysql-test/var/4/log/mysqld.1.err
ok

Make MTR treat failed warning check as a regular test failure and dump the whole error log.

Tags: ci upstream
Laurynas Biveinis (laurynas-biveinis)
tags: added: ci upstream
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

     https://github.com/percona/percona-server/pull/1611
     https://github.com/percona/percona-server/pull/1612
     https://github.com/percona/percona-server/pull/1613

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1792

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.