Successful doublewrite recovery should not be a warning

[Laurynas Biveinis]

Crash testcases might fail with the following, 5.6 trunk:

rpl.rpl_sync 'stmt' w2 [ fail ] Found warnings/errors in server log file!
        Test ended at 2016-08-31 13:28:07
line
InnoDB: Warning: database page corruption or a failed
^ Found warnings in /mnt/workspace/percona-server-5.6-trunk/BUILD_TYPE/debug/Host/centos6-64/build/mysql-test/var/2/log/mysqld.2.err
ok

This does not indicate any real problem but is rather a sign of expected doublewrite buffer operation. Instead of adding a suppression to each affected testcase, the message should be downgraded from Warning severity, similar to WebScaleSQL: https://github.com/webscalesql/webscalesql-5.6/commit/71abb720c08b640ecd85c849c1ee8f90892b6cad

[Laurynas Biveinis (laurynas-biveinis)]

This will make bug 16139886 fix obsolete and it should be reverted

[Laurynas Biveinis (laurynas-biveinis)]

     https://github.com/percona/percona-server/pull/1004
     https://github.com/percona/percona-server/pull/1005

[Laurynas Biveinis (laurynas-biveinis)]

Seen on 5.5 too:

main.group_commit_crash w2 [ fail ] Found warnings/errors in server log file!
        Test ended at 2017-05-04 08:43:15
line
InnoDB: Warning: database page corruption or a failed
^ Found warnings in /mnt/workspace/percona-server-5.5-trunk/BUILD_TYPE/debug/Host/debian-wheezy-x32/mysql-test/var/2/log/mysqld.1.err
ok

[Laurynas Biveinis (laurynas-biveinis)]

https://github.com/percona/percona-server/pull/1698

[Shahriyar Rzayev (rzayev-sehriyar)]

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