metrics: Increase minpercent range for clh tests

We have a new metrics machine and environment
and the fio write.bw and iperf3 parallel.Results
tests failed for clh, as below
the minimum range, so increase the
minpercent to try and get it stable

Signed-off-by: stevenhorsman <steven@uk.ibm.com>
This commit is contained in:
stevenhorsman 2025-02-27 14:50:54 +00:00
parent f81c85e73d
commit ef0e8669fb

View File

@ -121,7 +121,7 @@ description = "measure sequential write throughput using fio"
checkvar = "[.\"fio\".\"Results sequential\"] | .[] | .[] | .write.bw | select( . != null )"
checktype = "mean"
midval = 307948
minpercent = 20.0
minpercent = 40.0
maxpercent = 20.0
[[metric]]
@ -199,7 +199,7 @@ description = "measure container parallel bandwidth using iperf3"
checkvar = ".\"network-iperf3\".Results | .[] | .parallel.Result"
checktype = "mean"
midval = 57516472021.90
minpercent = 20.0
minpercent = 40.0
maxpercent = 20.0
[[metric]]
@ -211,6 +211,6 @@ description = "iperf"
# within (inclusive)
checkvar = ".\"network-iperf3\".Results | .[] | .jitter.Result"
checktype = "mean"
midval = 0.04
midval = 0.02
minpercent = 70.0
maxpercent = 60.0