From ea24d78868072c5c3977d46a643d3129efbcd648 Mon Sep 17 00:00:00 2001 From: yatsenko Date: Thu, 13 Aug 2026 11:08:52 -0700 Subject: [PATCH] run-vmtest: skip splat check without test_progs --- run-vmtest/README.md | 3 +++ run-vmtest/run-bpf-selftests.sh | 6 +++++- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/run-vmtest/README.md b/run-vmtest/README.md index c489fb5..1bebe63 100644 --- a/run-vmtest/README.md +++ b/run-vmtest/README.md @@ -47,6 +47,9 @@ hung tasks and lockups. A hit adds a `kernel_splats` row to `exitstatus`, which turns the run red like any other failing test group. Anything fatal panics the VM instead, and fails the job on its own. +The check runs for the default suite or when the requested runners include +`test_progs`. Veristat-only runs skip it. + The action carries no patterns. What a splat is, and what is benign, is policy that changes per arch and per kernel, so it lives with the configs. Two files of extended regexes, one per line, `#` comments and blank lines ignored, named diff --git a/run-vmtest/run-bpf-selftests.sh b/run-vmtest/run-bpf-selftests.sh index c598354..da4af1f 100755 --- a/run-vmtest/run-bpf-selftests.sh +++ b/run-vmtest/run-bpf-selftests.sh @@ -178,4 +178,8 @@ else done fi -"${SCRIPT_DIR}/check-kernel-splats.sh" +if [ ${#TEST_NAMES[@]} -eq 0 ] || [[ "${TEST_NAMES[*]}" == *test_progs* ]]; then + "${SCRIPT_DIR}/check-kernel-splats.sh" +else + echo "Skipping kernel splat check: test_progs not requested" +fi