Abhijat Malviya
Abhijat Malviya
I introduced deadlock artificially at different points in test but cannot reproduce the crash. Closing as it has not recurred in several weeks, will reopen if it happens again
there is a crash in `raxNext` when defragmenting a rax tree, probably related to the new move ctor added for the iterator. eta: should be fixed now by pretending to...
this one always happens with #6200 , still keeping it open but it is highly likely it is the same issue as the other failing test in the linked issue
@vyavdoshenko do I need to set some specific number of proactor threads? With 1 and 2 threads I cannot reproduce this locally. I also tried higher keys and iterations ```...
The problem with this test might be that the connection drop happens _while_ the second attempt is starting, when we expect to find the LSN out of the journal, but...
Maybe the body of the test should be repeated for a timeout until the error is seen, as it is the test can randomly fail depending on when the connection...