Comment 8 for bug 670356

Revision history for this message
Michael Widenius (monty) wrote :

Have run test case for some hours with latest 5.1 tree without problems.
I observed and fixed a similar error when working on the test case for the previous recovery bug, so I assume this is now also fixed.