Retry for stale reads in KV CAS chaos test#4769
Conversation
derekcollison
left a comment
There was a problem hiding this comment.
Prefer to leave direct gets but you can use checkFor() helper to wait for a certain period of time for the get to be current.
6ad58b4 to
a743862
Compare
|
@derekcollison updated to leave (2 commits for easier review, squashable on merge) |
a743862 to
564661c
Compare
|
Updated indentation in 2nd commit |
564661c to
88a10b1
Compare
|
Just rebased, the Jenkins error comes from Run non JetStream/MQTT tests from the server package:: |
derekcollison
left a comment
There was a problem hiding this comment.
One comment on the allow direct update to false.
88a10b1 to
136687e
Compare
|
Can we check the failures, seems all tests fails so probably failed staticcheck or something. Also, @mprimi is this the test that shows reset you wanted us to look at? |
|
@derekcollison this got stale, I'll rebase. The failing RAFT i mentioned is a different (draft) PR: #4626 |
Signed-off-by: Marco Primi marco@synadia.com
When detecting a stale value, retry rather than fail immediately. Signed-off-by: Marco Primi marco@synadia.com
Signed-off-by: Marco Primi marco@synadia.com
136687e to
09ba556
Compare
|
Freshly rebased on top of latest |
|
Chaos tests were removed in #5455, like mentioned:
|
Relax KV CAS test which was failing immediately upon reading a key with a revision which is known to be stale.
Instead, retry the read until a newer version is returned.
Signed-off-by: Marco Primi marco@synadia.com