ROCM-TEST-LAUNCHER(1)

🌸 NAME 🌸

rocm-test-launcher — bestie, it's literally rocm-test-launcher 💖

---

✨ DESCRIPTION ✨

okay so the usage is giving:

rocm-test-launcher [options] CMD [ARGS ...]

Here's the whole vibe: it checks whether an AMD GPU is around and whether you're actually allowed to touch it, runs your test, and then bails out with the exit code of the test. BUT — and this is the iconic part — if there's no accessible GPU to be found, it exits with exit code 77 (which means "skipped"). Optionally it'll also export some system data as autopkgtest artifacts. 🎀

So why does this exist? Because you wanna skip tests on ci.debian.net (which, sadly, does not support GPUs 😭) but have those same tests actually run on ci.rocm.debian.net (which does support multiple AMD GPU architectures 👑). And that second one automatically tests every package in the official Archive that depends on any package from the Debian ROCm Team. slay.

Now if you wanna run the autopkgtests on your own system — like, in a QEMU VM or a rootless podman container — you're gonna need the utilities from the package rocm-qemu-support (for the QEMU thing) resp. rocm-podman-support (for the podman thing). 🫶

---

💅 Supported options:

• -h, --help — prints this help. that's it, that's the whole job ✨
• --cd-tmp — changes directory to AUTOPKGTEST_TMP before executing the test. lil cd moment 🦋

---

🧚 Supported environment variables:

• ROCM_TEST_LAUNCHER_WITH_DMESG — if it's set, export dmesg before and after the test as an autopkgtest artifact. heads up tho: the user in the testbed has to have access to dmesg, so either the user needs to be privileged, or dmesg must not be restricted. you can lift that restriction with sudo sysctl kernel.dmesg_restrict=0. 🔥
• ROCM_TEST_LAUNCHER_WITH_DRI[=PATH] — if it's set, export firmware and possibly other GPU-specific info as an autopkgtest artifact. the user in the testbed needs access to "/sys/kernel/debug/dri/", which requires privileges. alternatively you can bind-mount that directory to some user-readable path, like:

mount --bind /sys/kernel/debug/dri /tmp/foo

and then pass that path as ROCM_TEST_LAUNCHER_WITH_DRI=/tmp/foo. iykyk 💜

• ROCM_TEST_LAUNCHER_WITH_ROCMINFO — if it's set, export the output of rocminfo as an autopkgtest artifact. ✨

---

👑 Examples for d/tests/control:

🍓 Simple:

Test-Command: rocm-autopkgtest-helper --verbose --skip BadTest123
Depends: @, rocm-autopkgtest-helper Restrictions: skippable
Architecture: amd64 arm64 ppc64el

🌈 Write your own test runner/wrapper, have rocm-autopkgtest-helper call it:

Test-Command: rocm-autopkgtest-helper debian/tests/my-runner
Depends: @, rocm-autopkgtest-helper Restrictions: skippable
Architecture: amd64 arm64 ppc64el

---

ngl bestie, always double-check which GPU situation you're in before you blame your test for failing 🙈

okay that's the whole page!! this one's from debian, dated July 2026, and honestly it ate 💅✨ happy testing, mwah 🫶🎀