From e946d9d5d35dc1e80264f9fb05d9d69782bd68f6 Mon Sep 17 00:00:00 2001 From: stevenhorsman Date: Thu, 9 Jan 2025 09:22:23 +0000 Subject: [PATCH 1/2] metrics: qemu: Increase latency test range After the kernel version bump, in the latest nightly run https://github.com/kata-containers/kata-containers/actions/runs/12681309963/job/35345228400 The sequential read throughput result was 79.7% of the expected (so failed) and the sequential write was 84% of the expected, so was fairly close, so increase their minimum ranges to make them more robust. Signed-off-by: stevenhorsman --- .../ci_worker/checkmetrics-json-qemu-kata-metric8.toml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/metrics/cmd/checkmetrics/ci_worker/checkmetrics-json-qemu-kata-metric8.toml b/tests/metrics/cmd/checkmetrics/ci_worker/checkmetrics-json-qemu-kata-metric8.toml index 9ca7225af2..94bc4ee2e3 100644 --- a/tests/metrics/cmd/checkmetrics/ci_worker/checkmetrics-json-qemu-kata-metric8.toml +++ b/tests/metrics/cmd/checkmetrics/ci_worker/checkmetrics-json-qemu-kata-metric8.toml @@ -108,7 +108,7 @@ description = "measure sequential read throughput using fio" checkvar = "[.\"fio\".\"Results sequential\"] | .[] | .[] | .read.bw | select( . != null )" checktype = "mean" midval = 327066.8 -minpercent = 20.0 +minpercent = 30.0 maxpercent = 20.0 [[metric]] @@ -121,7 +121,7 @@ description = "measure sequential write throughput using fio" checkvar = "[.\"fio\".\"Results sequential\"] | .[] | .[] | .write.bw | select( . != null )" checktype = "mean" midval = 309023.65 -minpercent = 20.0 +minpercent = 30.0 maxpercent = 20.0 [[metric]] From aaae5b6d0fdad8b1a98f4ff138b8edae567f8c11 Mon Sep 17 00:00:00 2001 From: stevenhorsman Date: Thu, 9 Jan 2025 11:25:41 +0000 Subject: [PATCH 2/2] metrics: clh: Increase network-iperf3 range We hit a failure with: ``` time="2025-01-09T09:55:58Z" level=warning msg="Failed Minval (0.017600 > 0.015000) for [network-iperf3]" ``` The range is very big, but in the last 3 test runs I reviewed we have got a minimum value of 0.015s and a max value of 0.052, so there is a ~350% difference possible so I think we need to have a wide range to make this 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 deca760eb3..50d4faf24c 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.044 -minpercent = 60.0 -maxpercent = 50.0 +midval = 0.04 +minpercent = 70.0 +maxpercent = 60.0