From 1022d8d26062ec807acf091c114ad030a6e74044 Mon Sep 17 00:00:00 2001 From: stevenhorsman Date: Fri, 14 Mar 2025 14:54:30 +0000 Subject: [PATCH] metrics: Update range for clh tests In ef0e8669fb75023dde90fc345fa8d812d6985bb5 we had been seeing some significantly lower minvalues in the jitter.Result test, so I lowered the mid-value rather than having a very high minpercent, but it appears that the variability of this result is very high, so we are still getting the occasional high value, so reset the midval and just have a bigger ranges on both sides, to try and keep the test stable. Signed-off-by: stevenhorsman --- .../ci_worker/checkmetrics-json-clh-kata-metric8.toml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tests/metrics/cmd/checkmetrics/ci_worker/checkmetrics-json-clh-kata-metric8.toml b/tests/metrics/cmd/checkmetrics/ci_worker/checkmetrics-json-clh-kata-metric8.toml index 5c9f126dd..3fafbc312 100644 --- a/tests/metrics/cmd/checkmetrics/ci_worker/checkmetrics-json-clh-kata-metric8.toml +++ b/tests/metrics/cmd/checkmetrics/ci_worker/checkmetrics-json-clh-kata-metric8.toml @@ -211,6 +211,6 @@ description = "iperf" # within (inclusive) checkvar = ".\"network-iperf3\".Results | .[] | .jitter.Result" checktype = "mean" -midval = 0.02 -minpercent = 70.0 -maxpercent = 60.0 +midval = 0.04 +minpercent = 85.0 +maxpercent = 80.0