ci: Tightening warning condition in dmesg checks

2026-05-03T23:58:15+00:00

The boot-time RETBleed: WARNING: Spectre v2 mitigation... line matches the broad WARNING: regex. The intent of that pattern was to catch kernel WARN_ON() splats, which always begin with WARNING: CPU:. We can tighten checks, to avoid false positive. Signed-off-by: Denys Fedoryshchenko

ci: fail workflows on kernel issues found in dmesg

2026-05-02T12:07:57+00:00

Recently i wasted several hours searching bug in workflows/userspace. Turned out in dmesg we had highly visible WARNING that we dont watch. After each test run, dump dmesg and grep for canonical kernel-issue markers (WARNING, BUG, Oops, kernel panic, GPF, KASAN, kernel UBSAN, soft/hard lockup, hung tasks, bad page state, invalid opcode). Fail the job if any are present, with a GitHub Actions error annotation. Until now, kernel WARNs from out-of-tree drivers (e.g. vlan_mon tripping the new ETH_P_ALL ptype_head WARN_ON in 6.6+) were silently swallowed by the existing 'Display processes and dmesg after tests' steps -- visible only if a human inspected the log. The check runs with if: always() so it triggers both on test failure and on test completion. Applied to all four workflows that load kernel modules: run-tests-asan-ubsan.yml, run-tests.yml (Test-in-Qemu, Test-in-Alpine, Test-in-GH, Test-in-GH-Coverage), run-tests-32bit.yml, and run-tests-bigendian.yml. P.S. Some whitespace churn included. Signed-off-by: Denys Fedoryshchenko

ci: update alpine links

2024-12-11T00:36:32+00:00

ci: run tests on x86_32 platform (alpine vm)

2024-11-30T23:26:38+00:00

accel-ppp.git/.github/workflows/run-tests-32bit.yml, branch sstp-alloc-invariant

ci: Tightening warning condition in dmesg checks

ci: fail workflows on kernel issues found in dmesg

ci: update alpine links

ci: run tests on x86_32 platform (alpine vm)