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.
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.