From b2e4155f54d335d7a6b0764ef963eaf5ef863f8f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Viktor=20S=C3=B6derqvist?= Date: Sun, 19 Jan 2025 19:23:00 +0100 Subject: [PATCH] Lower latenct-monitor-threashold in expire-cycle test case (#1584) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The test case checks for expire-cycle in LATENCY LATEST, but with the new hash table, the expiry-cycle is too fast to be logged by latency monitor. Lower the latency monitor threshold to make it more likely to be logged. Fixes #1580 --------- Signed-off-by: Viktor Söderqvist --- tests/unit/latency-monitor.tcl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/unit/latency-monitor.tcl b/tests/unit/latency-monitor.tcl index e4f45389d7..cabb90d382 100644 --- a/tests/unit/latency-monitor.tcl +++ b/tests/unit/latency-monitor.tcl @@ -143,7 +143,7 @@ tags {"needs:debug"} { } ;# tag test {LATENCY of expire events are correctly collected} { - r config set latency-monitor-threshold 20 + r config set latency-monitor-threshold 1 r config set lazyfree-lazy-expire no r flushdb if {$::valgrind} {set count 100000} else {set count 1000000}