Re: [PATCH] testing: bump mips64el cross to bookworm and allow to fail

["Alex Bennée" <alex.bennee@linaro.org>]

Thomas Huth <thuth@redhat.com> writes:

> On 23/09/2024 10.15, Alex Bennée wrote:
>> The mips64el cross setup is very broken for bullseye which has now
>> entered LTS support so is unlikely to be fixed. While we still can't
>> build the container for bookworm due to a single missing dependency
>> that will hopefully get fixed in due course. For the sake of keeping
>> the CI green we mark it as allow_fail for the time being.
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> Cc: Michael Tokarev <mjt@tls.msk.ru>
>> ---
> ...
>> @@ -143,6 +140,7 @@ RUN export DEBIAN_FRONTEND=noninteractive && \
>>                         libvdeplug-dev:mips64el \
>>                         libvirglrenderer-dev:mips64el \
>>                         libvte-2.91-dev:mips64el \
>> +                      libxdp-dev:mips64el \
>>                         libzstd-dev:mips64el \
>>                         nettle-dev:mips64el \
>>                         systemtap-sdt-dev:mips64el \
>
> We could also do a temporary manual hack and remove the problematic
> packages from the list that cause the failure. I guess removing
> libdrm-dev:mips64el , libgtk-3-dev:mips64el and the SDL2 packages
> might help to avoid that the mesa stuff gets installed (which causes
> the trouble)...
> Of course this will be overwritten the next time someone runs lcitool
> again, but with a little bit of luck, Debian already got fixed at that
> point in time. What do you think?

I was hoping the blockage would get cleared by now but I guess not. If
the distros no longer have enough eyeballs to care about mips64el and we
have it as Odd Fixes then I think the allow_fail approach allows us to
move forward without manual hacks.

If the CI runs and is green great, if not it doesn't hold anything up.

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro