Comment 6 for bug 940972

As I'm running through the test suite there are a lot of things that are stopping on failed replication. I've had to restart it several times in the last run against the branch you mentioned. I think it really is mandatory to have a check that the test didn't break replication; and tests for tools that do anything with replication, such as pt-table-checksum and pt-heartbeat, probably need to have a "replication_is_ok()" test first thing, which either passes or the whole test bails out. Otherwise we will never be able to run these reliably in an automated fashion; test runs will just hang and not complete.