This test is still hanging on some debug platfotforms probably due to slightly diffferent memory allocation patterns. The test was originally designed to reproduce a storage engine issue in 3.6.5. It's should be possible to lower the number of updates in this test as long as we are still able to trigger the bug on a 3.6.5 binary.