pub const KERNEL_HELP_NO_RAW: &str = "Kernel identifier — one of: \
(1) an exact version (`6.14.2`, `6.15-rc3`), a major.minor prefix \
(`6.14`, latest patch in the series), or a bare major (`6`, latest \
`6.x`); \
(2) an inclusive version range (`6.12..6.14` or `6.12..=6.14`); \
(3) a git source (`git+URL#tag=NAME`, `git+URL#branch=NAME`, or \
`git+URL#sha=<40-hex>`); \
(4) a source directory path (`./linux`, `~/linux`, or an absolute path); \
(5) a local kernel package (`*.rpm` / `*.deb` / `*.pkg.tar.zst`, one \
file per `--kernel`); \
(6) a prebuilt distro kernel — `fedora` / `fedora-44` / `f44`, \
`ubuntu` / `ubuntu-24.04` (resolves to the latest LTS HWE kernel), \
`amazonlinux` / `amazonlinux-2023` / `al2023`, \
`steamos` / `steamos-3.8`, or `gke` / `gke-129` \
(official GKE COS kernel; x86_64 only; bare `gke` picks the newest \
image in Google's current GKE release notes, while `gke-129` tracks \
the newest promoted revision within COS milestone 129); or \
(7) a cache key (see `kernel list`). Raw \
image files are rejected. Source directories auto-build (can be slow \
on a fresh tree); versions auto-download from kernel.org on cache \
miss; distro kernels download official kernel + debuginfo/source artifacts \
(cached like a built kernel). Ubuntu splits its \
image and modules across two debs, so a modular Ubuntu image needs the \
`ubuntu` distro form (which downloads both) rather than a single local \
`.deb`. The flag is REPEATABLE on `test`, `coverage`, and `llvm-cov` \
— passing multiple `--kernel` flags fans the gauntlet across every \
resolved kernel; each (test × scenario × topology × kernel) \
tuple becomes a distinct nextest test case so nextest's parallelism, \
retries, and `-E` filtering work natively. Ranges expand to every \
`stable` and `longterm` release inside `[START, END]` inclusive \
(mainline / linux-next dropped). Git branch and tag sources use \
the same exact-ref, depth-one in-process gix fetch on every host; \
only an explicit immutable GitHub SHA uses codeload. Same-content \
concurrent callers share one fetch and build. In contrast, `ktstr shell` accepts a single \
kernel only — pass exactly one `--kernel`.";Expand description
Help text for --kernel in contexts that reject raw image files:
cargo ktstr test, cargo ktstr coverage, cargo ktstr llvm-cov,
and ktstr shell. Matches
KernelResolvePolicy { accept_raw_image: false, .. }.
Raw images are rejected here because these commands depend on a
matching vmlinux and the cached kconfig fragment alongside the
image (test/coverage need BTF, ktstr shell reuses the cache
entry for kconfig discovery). A bare bzImage/Image passed
directly carries neither, so silently accepting it would produce
hard-to-diagnose mid-run failures.
cargo ktstr shell accepts raw images because its flow does not
need that companion metadata; see KERNEL_HELP_RAW_OK.