Re: Running autopkgtests with AMD GPUs with rocm-test-launcher
On 2025-06-20 08:28, Cordell Bloor wrote:
> On 2025-06-17 14:13, Christian Kastner wrote:
>> It would be simpler to keep a master copy somewhere and either use that
>> to run the tests, or symlink to it if necessary.
>>
>> runner: /usr/share/pkg-rocm-tools/bin/run-tests
>> invocation: /usr/share/pkg-rocm-tools/bin/run-tests <package>
>>
>> or
>>
>> symlink /usr/libexec/rocm/<package>/run-tests to that, and have
>> <package> inferred from the pwd.
>>
>> Or both.
>
> I think the main difficulty is that /something/ is going to have to
> handle categorizing and invoking the tests for each library and that
> 'something' is going to therefore end up looking slightly different for
> almost every library. If we isolate the 'something' so that we can reuse
> a single shared script, we're going to end up having to define an
> interface between the shared and the unique parts.
Hm, I was assuming that this categorization was supplied by upstream and
standardized across the ROCm ecosystem. You mentioned earlier on the
categories:
On 2025-06-12 02:57, Cordell Bloor wrote:
> The filter categories are chosen because there are corresponding options
> upstream for all libraries that we can draw from [...]
I'm OK with sticking to copying a script for now until we have a clear
solution.
Best,
Christian
Reply to: