Skip to content

run-vmtest: retire the legacy veristat runner - #241

Merged
theihor merged 5 commits into
mainfrom
run-vmtest-cleanup
Nov 13, 2026
Merged

theihor merged 5 commits into
mainfrom
run-vmtest-cleanup

Conversation

@theihor

@theihor theihor commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

BPF CI now supplies its veristat guest through VMTEST_SCRIPT
(kernel-patches/vmtest#551, merged).

  • Remove the legacy run_veristat test and its four corpus configs.
  • Scope BPF selftest preparation, bpftool checks and JSON summaries to the
    BPF selftest guest.
  • Run lint and action tests on pushes to main.
  • Remove the obsolete incremental-build test workflow and allow intentional
    KASAN-for-JIT selftest splats.

Bash syntax, ShellCheck -S error, and the existing action tests pass locally.

The dedicated test workflow is no longer needed. Delete it along
with the status badge in the action's README, which linked to it.

Signed-off-by: Ihor Solodrai <ihor.solodrai@linux.dev>
Port the block added by kernel-patches/vmtest#520. libbpf/ci carries
its own copy of these configs and never received it, so the expected
KASAN reports from the `kasan` selftest failed the splat check on
libbpf/ci runs (e.g. run 42701280551) even though the test itself
passed.

Signed-off-by: Ihor Solodrai <ihor.solodrai@linux.dev>
The lint and action test workflows run on pushes to master, but the
default branch is main. Changes are checked in pull requests and never
again after they land.

Filter pushes on main, as the test workflow does.

Signed-off-by: Ihor Solodrai <ihor.solodrai@linux.dev>
Custom VM scripts currently inherit the LATEST bpftool check and
selftest JSON reporting. This makes unrelated workloads require the
kernel selftest source and can report stale selftest results.

Select the guest before preparing BPF selftests and use that selection
to gate bpftool checks and summaries. Keep the config hook ability to
override the bpftool default.

Signed-off-by: Ihor Solodrai <ihor.solodrai@linux.dev>
BPF CI now measures its veristat corpora with its own guest script,
passed through VMTEST_SCRIPT, and no longer selects the run_veristat
test. The runner has no other known caller: it is not in the default
test list and only works with BPF CI's per-corpus configs.

Remove run_veristat and its environment from run-bpf-selftests.sh,
along with the run_veristat configs synced from kernel-patches/vmtest,
which removed them as well.

Signed-off-by: Ihor Solodrai <ihor.solodrai@linux.dev>
@theihor
theihor merged commit 32c128e into main Nov 13, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant