Skip to content

Skip the drm_sched and ratelimit KUnit suites in M14 - #61

Merged
tamnd merged 1 commit into
mainfrom
kunit-skip
Oct 3, 2026
Merged

tamnd merged 1 commit into
mainfrom
kunit-skip

Conversation

@tamnd

@tamnd tamnd commented Oct 3, 2026

Copy link
Copy Markdown
Owner

The DRM scheduler tests and the ratelimit stress test fail under TCG on a loaded host no matter which GCC built the kernel (#52). They made cells flaky and even dropped era cells to L6, which then left every other column in the row with a bad reference. KUNIT_ALL_TESTS hides both options, so the fragment cannot turn them off the usual way.

A fragment can now carry a # gk:kunit-skip <module>... line. The KUnit boot turns that into kunit.filter=module!=a,module!=b kunit.filter_action=skip, so the suites still show in the log as skipped instead of disappearing. M14 skips drm_sched_tests and test_ratelimit. The smoke boot is unchanged.

Since the line is part of the fragment text, it changes the M14 config digest and the M14 cells run again. Spec 07 describes the directive next to the KUNIT_FAULT_TEST paragraph.

Checked on server2: fmt, clippy with -D warnings, tests and the style script all pass.

@tamnd tamnd added this to the G1: the current stripe milestone Oct 3, 2026
@tamnd tamnd added kind/bug Something produces a wrong cell, verdict or report area/boot QEMU rig, gk-init, smoke suites and KUnit labels Oct 3, 2026
@tamnd
tamnd merged commit 4c7de11 into main Oct 3, 2026
4 checks passed
@tamnd
tamnd deleted the kunit-skip branch October 3, 2026 01:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/boot QEMU rig, gk-init, smoke suites and KUnit kind/bug Something produces a wrong cell, verdict or report

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant