metrics: Increase ranges range for qemu failing tests

We've also seen the qemu metrics tests are failing due to the results
being slightly outside the max range for network-iperf3 parallel and minimum for network-iperf3 jitter tests on PRs that have no code changes,
so we've increase the bounds to not see false negatives.

Signed-off-by: stevenhorsman <steven@uk.ibm.com>
This commit is contained in:
stevenhorsman 2024-11-29 10:52:16 +00:00
parent 4011071526
commit b87b4b6756

View File

@ -199,8 +199,8 @@ description = "measure container parallel bandwidth using iperf3"
checkvar = ".\"network-iperf3\".Results | .[] | .parallel.Result"
checktype = "mean"
midval = 52644229340.0
minpercent = 20.0
maxpercent = 20.0
minpercent = 25.0
maxpercent = 25.0
[[metric]]
name = "network-iperf3"
@ -211,6 +211,6 @@ description = "iperf"
# within (inclusive)
checkvar = ".\"network-iperf3\".Results | .[] | .jitter.Result"
checktype = "mean"
midval = 0.041
minpercent = 50.0
maxpercent = 50.0
midval = 0.040
minpercent = 60.0
maxpercent = 60.0