Describe the bug
The problem is that the test was introduced before "Flaky Check" and could have never worked if run multiple times in one runner. We revealed it while fixing another small issue in this integration test.
How to reproduce
sudo ./tests/integration/runner --binary <binary_name> --base-configs-dir path-to-config "test_quorum_inserts/test.py::test_insert_quorum_with_keeper_loss_connection" --count 2
Error message and/or stacktrace
> assert quorum_fail_future.exception() is None
E AssertionError: assert QueryTimeoutExceedException('Client timed out!') is None
E + where QueryTimeoutExceedException('Client timed out!') = <bound method Future.exception of <Future at 0x7dcd615b2440 state=finished raised QueryTimeoutExceedException>>()
E + where <bound method Future.exception of <Future at 0x7dcd615b2440 state=finished raised QueryTimeoutExceedException>> = <Future at 0x7dcd615b2440 state=finished raised QueryTimeoutExceedException>.exception
test_quorum_inserts/test.py:411: AssertionError
Fail point wasn't disabled for some reason.
Describe the bug
The problem is that the test was introduced before "Flaky Check" and could have never worked if run multiple times in one runner. We revealed it while fixing another small issue in this integration test.
How to reproduce
Error message and/or stacktrace
Fail point wasn't disabled for some reason.