summaryrefslogtreecommitdiff
path: root/tests/cluster
diff options
context:
space:
mode:
authorMadelyn Olson <34459052+madolson@users.noreply.github.com>2022-01-25 23:59:53 -0800
committerGitHub <noreply@github.com>2022-01-26 09:59:53 +0200
commitf6b76e50adde73070a139a847191e1927fef9747 (patch)
tree857a4373a0fad67c4a6cced1dd67393fa0d2c43f /tests/cluster
parent4491ee1805ea9044747af22a7abba9bac00c671a (diff)
downloadredis-f6b76e50adde73070a139a847191e1927fef9747.tar.gz
Change expression to look for at least one limit exceeded (#10173)
This is an attempt to fix some of the issues with the cluster mode tests we are seeing in the daily run. The test is trying to incrementally adds a bunch of publish messages, expecting that eventually one of them will overflow. The tests stops one of the processes, so it expects that just that one Redis node will overflow. I think the test is flaky because under certain circumstances multiple links are getting disconnected, not just the one that is stalled.
Diffstat (limited to 'tests/cluster')
-rw-r--r--tests/cluster/tests/24-links.tcl2
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/cluster/tests/24-links.tcl b/tests/cluster/tests/24-links.tcl
index 92ce0f0be..d0ddea200 100644
--- a/tests/cluster/tests/24-links.tcl
+++ b/tests/cluster/tests/24-links.tcl
@@ -91,7 +91,7 @@ test "Disconnect link when send buffer limit reached" {
[catch {incr i} e] == 0 &&
[catch {$primary1 publish channel [prepare_value [expr 128*1024]]} e] == 0 &&
[catch {after 500} e] == 0 &&
- [get_info_field [$primary1 cluster info] total_cluster_links_buffer_limit_exceeded] eq 1
+ [get_info_field [$primary1 cluster info] total_cluster_links_buffer_limit_exceeded] >= 1
} else {
fail "Cluster link not freed as expected"
}