An innodb_stress test failure may result in gigabyte-sized logs

[laurynas-biveinis]

If a test in innodb_stress suite fails for any reason, it will cause a standard replication MTR test dump of master/slave statuses, and binlog events. The latter is unlimited, and innodb_stress tests are large, thus the dump can be easily in gigabytes. Oracle MySQL should be affected as well.

A fix would be to limit mysql-test/include/show_rpl_debug_info.inc SHOW BINLOG/RELAYLOG EVENTS to show the last X events, where X could be picked so that it still covers non-innodb_stress tests well (maybe 200 or so).

An example of such logs is at http://jenkins.percona.com/job/WebScaleSQL-param/27/BUILD_TYPE=release,Host=webscaletest/consoleText:

innodb_stress.innodb_stress_lra w4 [ fail ]
Test ended at 2015-08-08 06:37:47

CURRENT_TEST: innodb_stress.innodb_stress_lra
=== SHOW MASTER STATUS ===
...
*** SHOW BINLOG EVENTS on default ****
binlog_name = 'master-bin.000002'
SHOW BINLOG EVENTS IN 'master-bin.000002';
Log_name Pos Event_type Server_id End_log_pos Info
master-bin.000002 4 Format_desc 1 120 Server ver: 5.6.25-log, Binlog ver: 4
.... megabytes here ...
master-bin.000002 3057638 Xid 1 3057669 COMMIT /* xid=23421 /
...
** SHOW BINARY LOGS on default ****
SHOW BINARY LOGS;
Log_name File_size
slave-bin.000001 385800766

**** SHOW BINLOG EVENTS on default ****
binlog_name = 'slave-bin.000001'
SHOW BINLOG EVENTS IN 'slave-bin.000001';
Log_name Pos Event_type Server_id End_log_pos Info
slave-bin.000001 4 Format_desc 2 120 Server ver: 5.6.25-log, Binlog ver: 4
... gigabytes here....