Re: [igt-dev] [PATCH] tests/amdgpu: Add KFD IOCTL fuzzing test - Apologies for build failures

[vitaly prosyak <vprosyak@amd.com>]

[-- Attachment #1: Type: text/plain, Size: 2201 bytes --]

Hi Kamil,
Thank you so much for your explanation!
I spent quite some time searching the interface for those build results, copying and investigating links, and honestly started feeling a bit foolish for not being able to find the compilation status. It is a big relief to know that this feature is simply temporarily disabled at the moment due to the GitLab upgrade.
Regarding your previous response about the filtering mechanics — I haven't forgotten about it. I will review and reply to that topic as soon as I am back working on this specific task.
Thanks again for your time and help!
Best regards,
Vitaly


On 2026-05-14 11:06, Kamil Konieczny wrote:
> Hi vitaly,
> On 2026-05-07 at 00:08:18 -0400, vitaly prosyak wrote:
>> Hi Kamil,
>>
>> I apologize for the build failures in my recent amd_fuzzing_kfd patch series and the need for 3 additional fixup patches to address ARM cross-compilation issues.
>>
>> The failures were due to:
>> 1. Missing drm/drm.h include dependency on some systems
>> 2. Incomplete KFD IOCTL struct definitions on ARM (forward declarations only)
>> 3. KFD being x86/x86_64 specific (AMD GPUs not supported on ARM)
>>
>> I've now submitted fixes that:
>> - Add proper header dependencies and guards
>> - Restrict KFD tests to x86/x86_64 architectures only in meson.build
>> - Follow the same pattern as amd_kfd_dmabuf_unload.c
>>
>> I'm curious - is there a way to see build failure results from patchwork.freedesktop.org before patches are merged? I couldn't find build status information on the patchwork interface, but I'd like to catch these issues earlier in the future. If you could point me to where CI build results are posted, I would greatly appreciate it.
>>
>> Sorry again for the extra churn, and thank you for maintaining IGT!
>>
>> Best regards,
>> Vitaly 
>>
> I will talk with our CI, I hope they could reintroduce compilation
> step for different arch like armhf or arm64. We had pipeline
> with builds but that was disabled during recent GitLab upgrade,
> when no GitLab repos were available.
>
> Regards,
> Kamil
>
> PS. for reference how it was before:
> https://patchwork.freedesktop.org/series/138642/
> with status line from GitLab.Pipeline
>

[-- Attachment #2: Type: text/html, Size: 6996 bytes --]