Comment 228 for bug 1470250

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I'm still testing 1c8349a17 now. I increased the number of I/O threads to increase the change of triggering the bug. It's been running for almost 24 hours now. I'll let it run for up to 36 hours with this I/O load.

I agree that if 8321521 does turn out good, we would want to test 586fbce again to be sure about our results.