Hi Frederic, On 2024-10-08 21:08, PICCA Frederic-Emmanuel wrote: > I have a bunch of package, that I would like to instrument in order to use > the rocm autopkgtest ci.
I'm really glad to hear that! > Do you know what is the procedure to follow in order to add an autopkgtest > specificaly for this rocm-ci ? The most important thing is to check whether the rendering device /dev/kfd exists and is readable+writeable, and skip the tests if not. Otherwise tests fail on the official ci.debian.net. On ci.rocm.debian.net, user 'debci' is in group 'render' in all test environments, so tests get run there. A nice to have would be to dump dmesg before/after the test, and other system information, and export them as artifacts. This helps debugging amdgpu driver issues. But this is entirely optional. For now it would suffice to check for /dev/kfd permissions following the example that Cory linked [1]. > And inddeed how to have them run on the rocm-ci. This happens automatically for any package in the Archive that becomes a reverse dependency of any ROCm package. We can also track arbitrary packages (eg: if you'd like to test some grandchild reverse dependency). For example, we also trigger tests on kernel updates. Best, Christian PS: Note to myself, factor out our test preamble and postamble into a utility that people can just call as one-liners. On 2024-10-08 23:49, Cordell Bloor wrote: > [1]: > https://salsa.debian.org/rocm-team/rocrand/-/blob/debian/5.7.1-4/debian/tests/upstream-binaries?ref_type=tags#L16-26
