# Investigating Cirrus CI FreeBSD failures 6 messages from 2022-05-21 to 2022-06-02. Participants: Philippe Blain, Carlo Arenas, Ed Maste, Junio C Hamano, Johannes Schindelin. Thread: https://gitlist.dev/t/57907 ## Philippe Blain, 2022-05-21 00:38 Subject: Investigating Cirrus CI FreeBSD failures Message-ID: <9cc31276-ab78-fa8a-9fb4-b19266911211@gmail.com> URL: https://gitlist.dev/e/9cc31276-ab78-fa8a-9fb4-b19266911211%40gmail.com ``` Hi, I spent a bit of time investigating the Git Cirrus-CI failures on FreeBSD. It seems something goes wrong with the Perl installation, as most failures are in t9001-send-email.sh, and the error messages are: ld-elf.so.1: /usr/local/lib/perl5/5.32/mach/CORE/libperl.so.5.32: Undefined symbol "strerror_l@FBSD_1.6" The first instance is in t9001.6. (See for example [1]). I know next to nothing about Perl or FreeBSD, but simply changing our image to FreeBSD 13.0 makes all failures in t9001 disappear [2]: diff --git a/.cirrus.yml b/.cirrus.yml index 0d94d89f6c..d1ea14362f 100644 --- a/.cirrus.yml +++ b/.cirrus.yml @@ -9,7 +9,7 @@ freebsd_12_task: DEFAULT_TEST_TARGET: prove DEVELOPER: 1 freebsd_instance: - image_family: freebsd-12-2 + image_family: freebsd-13-0 memory: 2G install_script: pkg install -y gettext gmake perl5 vim Is this something that we should do ? Or should we stick to FreeBSD 12 and try to debug this installation problem ? Cheers, Philippe. [1] https://cirrus-ci.com/task/5856927879004160 [2] https://cirrus-ci.com/task/4597971764379648 ``` ## Carlo Arenas, 2022-05-21 00:52 Subject: Re: Investigating Cirrus CI FreeBSD failures Message-ID: URL: https://gitlist.dev/e/CAPUEspgdAos4KC-3AwYDd5p%2Bu0hGk73nGocBTFFSR7VB9%2BM5jw%40mail.gmail.com In-Reply-To: <9cc31276-ab78-fa8a-9fb4-b19266911211@gmail.com> ``` Reviewed-by: Carlo Marcelo Arenas Belón ``` ## Ed Maste, 2022-05-30 16:09 Subject: Re: Investigating Cirrus CI FreeBSD failures Message-ID: URL: https://gitlist.dev/e/CAPyFy2AETzTCJUtbxS%2BRmygajrUS5XUkZvF-1FVbJ67t61bJtg%40mail.gmail.com In-Reply-To: <9cc31276-ab78-fa8a-9fb4-b19266911211@gmail.com> ``` On Fri, 20 May 2022 at 20:38, Philippe Blain wrote: > > Hi, > > I spent a bit of time investigating the Git Cirrus-CI failures on FreeBSD. > It seems something goes wrong with the Perl installation, as most failures > are in t9001-send-email.sh, and the error messages are: > > ld-elf.so.1: /usr/local/lib/perl5/5.32/mach/CORE/libperl.so.5.32: Undefined symbol "strerror_l@FBSD_1.6" Ah, what happened here is that this is picking up the perl package built on 12.3 (i.e., the earliest supported FreeBSD 12.x) which added strerror_l. https://cgit.freebsd.org/src/commit/?id=d3912bec58d0b82509a0973cae02f156986d88fa > I know next to nothing about Perl or FreeBSD, but simply changing our image > to FreeBSD 13.0 makes all failures in t9001 disappear [2]: > > ... > Is this something that we should do ? Or should we stick to FreeBSD 12 > and try to debug this installation problem ? I expect this could have been addressed also by updating to 12.3. Cirrus also supports "matrix" so both could be tested. ``` ## Philippe Blain, 2022-05-30 20:15 Subject: Re: Investigating Cirrus CI FreeBSD failures Message-ID: URL: https://gitlist.dev/e/e31d26ad-3b0b-15c0-262f-4eee83220949%40gmail.com In-Reply-To: ``` Hi Ed, Le 2022-05-30 à 12:09, Ed Maste a écrit : > On Fri, 20 May 2022 at 20:38, Philippe Blain > wrote: >> >> Hi, >> >> I spent a bit of time investigating the Git Cirrus-CI failures on FreeBSD. >> It seems something goes wrong with the Perl installation, as most failures >> are in t9001-send-email.sh, and the error messages are: >> >> ld-elf.so.1: /usr/local/lib/perl5/5.32/mach/CORE/libperl.so.5.32: Undefined symbol "strerror_l@FBSD_1.6" > > Ah, what happened here is that this is picking up the perl package > built on 12.3 (i.e., the earliest supported FreeBSD 12.x) which added > strerror_l. > https://cgit.freebsd.org/src/commit/?id=d3912bec58d0b82509a0973cae02f156986d88fa OK, so it is expected that the Cirrus 12.2 image would install this newer version of the perl package which if I understand correctly is not compatible with this version ? Is there a way to tell pkg not to update packages to incompatible versions, or is the FreeBSD policy that as soon as a release is marked as unsupported, then no guarantee is made that things (like installing packages) continue working on that version ? > >> I know next to nothing about Perl or FreeBSD, but simply changing our image >> to FreeBSD 13.0 makes all failures in t9001 disappear [2]: >> >> ... >> Is this something that we should do ? Or should we stick to FreeBSD 12 >> and try to debug this installation problem ? > > I expect this could have been addressed also by updating to 12.3. > Cirrus also supports "matrix" so both could be tested. > For now we opted to just update to 12.3, see [1]. Thanks for your answer, Philippe. [1] https://lore.kernel.org/git/20220525125112.86954-1-levraiphilippeblain@gmail.com/ ``` ## Junio C Hamano, 2022-05-31 14:05 Subject: Re: Investigating Cirrus CI FreeBSD failures Message-ID: URL: https://gitlist.dev/e/xmqqczftx0e0.fsf%40gitster.g In-Reply-To: ``` Philippe Blain writes: >> Ah, what happened here is that this is picking up the perl package >> built on 12.3 (i.e., the earliest supported FreeBSD 12.x) which added >> strerror_l. >> https://cgit.freebsd.org/src/commit/?id=d3912bec58d0b82509a0973cae02f156986d88fa > > OK, so it is expected that the Cirrus 12.2 image would install this newer > version of the perl package which if I understand correctly is not compatible > with this version ? > > Is there a way to tell pkg not to update packages to incompatible versions, > or is the FreeBSD policy that as soon as a release is marked as unsupported, > then no guarantee is made that things (like installing packages) continue working > on that version ? Sorry for a noise, but I would also be curious to know, as it is quite unexpected for a packaging system to miss such a compatibility issue and for a distro to not care. >> I expect this could have been addressed also by updating to 12.3. >> Cirrus also supports "matrix" so both could be tested. > > For now we opted to just update to 12.3, see [1]. Indeed we did. Let's make sure we fast-track the topic down to 'master' and possibly to 'maint'. I do not think it is worth letting it sit in 'next' for a week, like we do for usual topics. Thanks. P.S. I'll be offline today (like every other Tuesday). ``` ## Johannes Schindelin, 2022-06-02 15:22 Subject: Re: Investigating Cirrus CI FreeBSD failures Message-ID: URL: https://gitlist.dev/e/nycvar.QRO.7.76.6.2206021721070.349%40tvgsbejvaqbjf.bet In-Reply-To: ``` Hi Junio, On Tue, 31 May 2022, Junio C Hamano wrote: > Philippe Blain writes: > > > For now we opted to just update to 12.3, see [1]. > > Indeed we did. Let's make sure we fast-track the topic down to 'master' > and possibly to 'maint'. I do not think it is worth letting it sit in > 'next' for a week, like we do for usual topics. I am very much in favor of merging this down into `maint`, as every PR run of GitGitGadget's PRs fails right now (and some new contributors already were worried about this). Thanks, Dscho ```