KDE Frameworks with failing CI (master) (29 January 2024)

[christoph at cullmann.io]

On 2024-02-03 08:57, Ben Cooksley wrote:
> On Wed, Jan 31, 2024 at 9:25 PM Ben Cooksley <bcooksley at kde.org>
> wrote:
> 
>> On Wed, Jan 31, 2024 at 9:06 AM Volker Krause <vkrause at kde.org>
>> wrote:
>> 
>>> On Dienstag, 30. Januar 2024 19:08:50 CET Ben Cooksley wrote:
>>>> On Wed, Jan 31, 2024 at 5:10 AM Volker Krause
>>> <vkrause at kde.org> wrote:
>>>>> On Dienstag, 30. Januar 2024 09:57:32 CET Ben Cooksley wrote:
>>>>>> On Tue, Jan 30, 2024 at 8:47 PM Sune Vuorela
>>> <nospam at vuorela.dk> wrote:
>>>>>> > On 2024-01-29, Albert Astals Cid <aacid at kde.org> wrote:
>>>>>> > > Bad news: 6 repositories have started failing
>>>>>> > >
>>>>>> > > baloo:
>>>>>> > > kconfig:
>>>>>> > > kcontacts
>>>>>> > > kfilemetadata:
>>>>>> > > ki18n:
>>>>>> > >
>>>>>> > > threadweaver:
>>>>>> > >   * FreeBSD tests are failing
>>>>>> >
>>>>>> > I haven't studied these, and don't know if they are
>>> frequent or
>>>>>> > occasional failures. I have seen, after the fbsd builder
>>> changes, that
>>>>>> > test execution times have gone up 20-50%. If it is big
>>> tests that is
>>>>>> > already close to the limit, then that might be the reason.
>>>>>> >
>>>>>> > Or for others with occasional timeout tests on freebsd.
>>>>>> 
>>>>>> Having a quick look at this, it seems that quite a few of
>>> those failures
>>>>>> are i18n related.
>>>>>> Given we are seeing locale warnings I have a suspicion that
>>> is the cause
>>>>> 
>>>>> of
>>>>> 
>>>>>> many of those failures.
>>>>> 
>>>>> For ki18n and kcontacts another possible cause could be the
>>> iso-codes
>>>>> translation catalogs missing. Are those by any chance packaged
>>> separately
>>>>> as
>>>>> on some Linux distributions?
>>>> 
>>>> I've checked and we do have iso-codes installed within the
>>> FreeBSD
>>>> containers.
>>>> The files are located at /usr/local/share/iso-codes/ though -
>>> will our
>>>> logic find them there?
>>> 
>>> Yes, the iso-codes data file are found, the tests would show very
>>> explicit
>>> error messages and fail in many more places otherwise. We however
>>> also need
>>> the corresponding translation catalogs, not just the data files.
>>> On Linux those
>>> are in /usr/share/locale/*/LC_MESSAGE/iso_3166*.mo (but often
>>> separately
>>> packaged and thus missing).
>> 
>> Those files are present, although in FreeBSD fashion they are at
>> /usr/local/share/ instead of /usr/share/:
>> 
>> /usr/local/share/locale/tr/LC_MESSAGES/iso_3166-1.mo
>> /usr/local/share/locale/tr/LC_MESSAGES/iso_3166-3.mo
>> /usr/local/share/locale/tr/LC_MESSAGES/iso_3166-2.mo
>> /usr/local/share/locale/tr/LC_MESSAGES/iso_3166.mo
>> /usr/local/share/locale/tr/LC_MESSAGES/iso_3166_2.mo
>> 
>> Confusingly, and in a way that probably doesn't help software:
>> 
>> [user at 399f8cd87e55 ~]$ ls -lah /usr/share/locale/tr_TR.UTF-8/
>> total 52
>> drwxr-xr-x    2 root wheel    8B Jan 30 10:28 .
>> drwxr-xr-x  197 root wheel  197B Jan 30 10:28 ..
>> -r--r--r--    1 root wheel   79K Jan 25 15:04 LC_COLLATE
>> lrwxr-xr-x    1 root wheel   19B Jan 25 15:04 LC_CTYPE ->
>> ../C.UTF-8/LC_CTYPE
>> -r--r--r--    1 root wheel  167B Jan 25 15:04 LC_MESSAGES
>> -r--r--r--    1 root wheel   34B Jan 25 15:04 LC_MONETARY
>> -r--r--r--    1 root wheel    6B Jan 25 15:04 LC_NUMERIC
>> -r--r--r--    1 root wheel  374B Jan 25 15:04 LC_TIME
> 
> The issue was figured out thanks to the work of frinring - who figured
> out that LC_ALL and LANGUAGE had been set in our FreeBSD containers.
> That has now been rectified, and the tests in several more Frameworks
> now pass.
> 
> (Leaving just Baloo and KFileMetaData as broken I believe)

Hi,

could it be that extended attributes don't work?

I think these tests rely on them.

Greetings
Christoph