You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test_stream_parity can fail if it's running on a slow disk (i.e., not SSD/ramdisk). This is bad because it's part of our make site_test suite, and presumably should pass even in less resource-heavy environments.
It could be that if there is replication lag at the time that the test starts, the master and replica have different current positions, which cause their events streams to not be equal.
The text was updated successfully, but these errors were encountered:
test_stream_parity can fail if it's running on a slow disk (i.e., not SSD/ramdisk). This is bad because it's part of our make site_test suite, and presumably should pass even in less resource-heavy environments.
The particular failure mode that I saw was:
@enisoc and I hypothesize that this is flaky because of the first two lines of the test:
It could be that if there is replication lag at the time that the test starts, the master and replica have different current positions, which cause their events streams to not be equal.
The text was updated successfully, but these errors were encountered: