Unstable rpl_percona_crash_resistant_rpl test

5.5:

http://jenkins.percona.com/job/percona-server-5.5-trunk/176/
http://jenkins.percona.com/job/percona-server-5.5-trunk/176/BUILD_TYPE=debug,Host=centos5-64/testReport/junit/%28root%29/rpl/rpl_percona_crash_resistant_rpl__row_/

CURRENT_TEST: rpl.rpl_percona_crash_resistant_rpl
mysqltest: In included file "./include/start_slave.inc":
included from ./include/start_slave.inc at line 34:
At line 34: query 'START SLAVE' failed: 1201: Could not initialize master info structure; more error messages can be found in the MySQL error log

The result from queries just before the failure was:
< snip >
SELECT COUNT(*) FROM t1;
COUNT(*)
2
SET GLOBAL debug="+d,crash_commit_before";
START SLAVE;
include/rpl_start_server.inc [server_number=2]
include/start_slave.inc
SELECT COUNT(*) FROM t1;
COUNT(*)
2
STOP SLAVE;
include/wait_for_slave_to_stop.inc
INSERT INTO t1 VALUES();
SELECT COUNT(*) FROM t1;
COUNT(*)
3
SET GLOBAL debug="+d,crash_innodb_after_prepare";
START SLAVE;
include/rpl_start_server.inc [server_number=2]
include/start_slave.inc

More results from queries before failure can be found in /home/jenkins/workspace/percona-server-5.5-trunk/BUILD_TYPE/debug/Host/centos5-64/Percona-Server/mysql-test/var/2/log/rpl_percona_crash_resistant_rpl.log

The error message suggests a corrupted master.info file after our intentional server crashes and our goal is to test the corruption of relay-log.info, not master.info. Will restructure the test so that slave I/O thread runs first, stops to flush master.info, SQL thread starts and crashes.

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