{"thread":{"id":"57907","subject":"Investigating Cirrus CI FreeBSD failures","startedAt":"2022-05-21T00:38:59Z","lastAt":"2022-06-02T15:22:53Z","messageCount":6,"participants":["Philippe Blain","Carlo Arenas","Ed Maste","Junio C Hamano","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"455663","messageId":"9cc31276-ab78-fa8a-9fb4-b19266911211@gmail.com","threadId":"57907","inReplyTo":null,"subject":"Investigating Cirrus CI FreeBSD failures","fromName":"Philippe Blain","fromEmail":"levraiphilippeblain@gmail.com","sentAt":"2022-05-21T00:38:53Z","receivedAt":"2022-05-21T00:38:59Z","isPatch":false,"sender":{"key":"levraiphilippeblain@gmail.com","avatar":"https://avatars.githubusercontent.com/u/44212482?v=4"},"body":"Hi,\n\nI spent a bit of time investigating the Git Cirrus-CI failures on FreeBSD.\nIt seems something goes wrong with the Perl installation, as most failures \nare in t9001-send-email.sh, and the error messages are:\n\nld-elf.so.1: /usr/local/lib/perl5/5.32/mach/CORE/libperl.so.5.32: Undefined symbol \"strerror_l@FBSD_1.6\"\n\nThe first instance is in t9001.6. (See for example [1]).\n\nI know next to nothing about Perl or FreeBSD, but simply changing our image\nto FreeBSD 13.0 makes all failures in t9001 disappear [2]:\n\n\ndiff --git a/.cirrus.yml b/.cirrus.yml\nindex 0d94d89f6c..d1ea14362f 100644\n--- a/.cirrus.yml\n+++ b/.cirrus.yml\n@@ -9,7 +9,7 @@ freebsd_12_task:\n DEFAULT_TEST_TARGET: prove\n DEVELOPER: 1\n freebsd_instance:\n- image_family: freebsd-12-2\n+ image_family: freebsd-13-0\n memory: 2G\n install_script:\n pkg install -y gettext gmake perl5 vim\n\nIs this something that we should do ? Or should we stick to FreeBSD 12\nand try to debug this installation problem ?\n\nCheers,\nPhilippe.\n\n[1] https://cirrus-ci.com/task/5856927879004160\n[2] https://cirrus-ci.com/task/4597971764379648\n"},{"id":"455664","messageId":"CAPUEspgdAos4KC-3AwYDd5p+u0hGk73nGocBTFFSR7VB9+M5jw@mail.gmail.com","threadId":"57907","inReplyTo":"9cc31276-ab78-fa8a-9fb4-b19266911211@gmail.com","subject":"Re: Investigating Cirrus CI FreeBSD failures","fromName":"Carlo Arenas","fromEmail":"carenas@gmail.com","sentAt":"2022-05-21T00:52:27Z","receivedAt":"2022-05-21T00:52:46Z","isPatch":false,"sender":{"key":"carenas@gmail.com","avatar":"https://avatars.githubusercontent.com/u/76036?v=4"},"body":"Reviewed-by: Carlo Marcelo Arenas Belón \n"},{"id":"456371","messageId":"CAPyFy2AETzTCJUtbxS+RmygajrUS5XUkZvF-1FVbJ67t61bJtg@mail.gmail.com","threadId":"57907","inReplyTo":"9cc31276-ab78-fa8a-9fb4-b19266911211@gmail.com","subject":"Re: Investigating Cirrus CI FreeBSD failures","fromName":"Ed Maste","fromEmail":"emaste@freebsd.org","sentAt":"2022-05-30T16:09:35Z","receivedAt":"2022-05-30T16:09:51Z","isPatch":false,"sender":{"key":"emaste@freebsd.org","avatar":"https://avatars.githubusercontent.com/u/1034582?v=4"},"body":"On Fri, 20 May 2022 at 20:38, Philippe Blain\n wrote:\n>\n> Hi,\n>\n> I spent a bit of time investigating the Git Cirrus-CI failures on FreeBSD.\n> It seems something goes wrong with the Perl installation, as most failures\n> are in t9001-send-email.sh, and the error messages are:\n>\n> ld-elf.so.1: /usr/local/lib/perl5/5.32/mach/CORE/libperl.so.5.32: Undefined symbol \"strerror_l@FBSD_1.6\"\n\nAh, what happened here is that this is picking up the perl package\nbuilt on 12.3 (i.e., the earliest supported FreeBSD 12.x) which added\nstrerror_l.\nhttps://cgit.freebsd.org/src/commit/?id=d3912bec58d0b82509a0973cae02f156986d88fa\n\n> I know next to nothing about Perl or FreeBSD, but simply changing our image\n> to FreeBSD 13.0 makes all failures in t9001 disappear [2]:\n>\n> ...\n> Is this something that we should do ? Or should we stick to FreeBSD 12\n> and try to debug this installation problem ?\n\nI expect this could have been addressed also by updating to 12.3.\nCirrus also supports \"matrix\" so both could be tested.\n"},{"id":"456378","messageId":"e31d26ad-3b0b-15c0-262f-4eee83220949@gmail.com","threadId":"57907","inReplyTo":"CAPyFy2AETzTCJUtbxS+RmygajrUS5XUkZvF-1FVbJ67t61bJtg@mail.gmail.com","subject":"Re: Investigating Cirrus CI FreeBSD failures","fromName":"Philippe Blain","fromEmail":"levraiphilippeblain@gmail.com","sentAt":"2022-05-30T20:15:37Z","receivedAt":"2022-05-30T20:16:05Z","isPatch":false,"sender":{"key":"levraiphilippeblain@gmail.com","avatar":"https://avatars.githubusercontent.com/u/44212482?v=4"},"body":"Hi Ed,\n\nLe 2022-05-30 à 12:09, Ed Maste a écrit :\n> On Fri, 20 May 2022 at 20:38, Philippe Blain\n> wrote:\n>>\n>> Hi,\n>>\n>> I spent a bit of time investigating the Git Cirrus-CI failures on FreeBSD.\n>> It seems something goes wrong with the Perl installation, as most failures\n>> are in t9001-send-email.sh, and the error messages are:\n>>\n>> ld-elf.so.1: /usr/local/lib/perl5/5.32/mach/CORE/libperl.so.5.32: Undefined symbol \"strerror_l@FBSD_1.6\"\n> \n> Ah, what happened here is that this is picking up the perl package\n> built on 12.3 (i.e., the earliest supported FreeBSD 12.x) which added\n> strerror_l.\n> https://cgit.freebsd.org/src/commit/?id=d3912bec58d0b82509a0973cae02f156986d88fa\n\nOK, so it is expected that the Cirrus 12.2 image would install this newer\nversion of the perl package which if I understand correctly is not compatible\nwith this version ?\n\nIs there a way to tell pkg not to update packages to incompatible versions,\nor is the FreeBSD policy that as soon as a release is marked as unsupported, \nthen no guarantee is made that things (like installing packages) continue working \non that version ?\n\n> \n>> I know next to nothing about Perl or FreeBSD, but simply changing our image\n>> to FreeBSD 13.0 makes all failures in t9001 disappear [2]:\n>>\n>> ...\n>> Is this something that we should do ? Or should we stick to FreeBSD 12\n>> and try to debug this installation problem ?\n> \n> I expect this could have been addressed also by updating to 12.3.\n> Cirrus also supports \"matrix\" so both could be tested.\n> \n\nFor now we opted to just update to 12.3, see [1].\n\nThanks for your answer,\n\nPhilippe.\n\n[1] https://lore.kernel.org/git/20220525125112.86954-1-levraiphilippeblain@gmail.com/\n"},{"id":"456389","messageId":"xmqqczftx0e0.fsf@gitster.g","threadId":"57907","inReplyTo":"e31d26ad-3b0b-15c0-262f-4eee83220949@gmail.com","subject":"Re: Investigating Cirrus CI FreeBSD failures","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2022-05-31T14:05:59Z","receivedAt":"2022-05-31T14:06:10Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Philippe Blain writes:\n\n>> Ah, what happened here is that this is picking up the perl package\n>> built on 12.3 (i.e., the earliest supported FreeBSD 12.x) which added\n>> strerror_l.\n>> https://cgit.freebsd.org/src/commit/?id=d3912bec58d0b82509a0973cae02f156986d88fa\n>\n> OK, so it is expected that the Cirrus 12.2 image would install this newer\n> version of the perl package which if I understand correctly is not compatible\n> with this version ?\n>\n> Is there a way to tell pkg not to update packages to incompatible versions,\n> or is the FreeBSD policy that as soon as a release is marked as unsupported, \n> then no guarantee is made that things (like installing packages) continue working \n> on that version ?\n\nSorry for a noise, but I would also be curious to know, as it is\nquite unexpected for a packaging system to miss such a compatibility\nissue and for a distro to not care.\n\n>> I expect this could have been addressed also by updating to 12.3.\n>> Cirrus also supports \"matrix\" so both could be tested.\n>\n> For now we opted to just update to 12.3, see [1].\n\nIndeed we did. Let's make sure we fast-track the topic down to\n'master' and possibly to 'maint'. I do not think it is worth\nletting it sit in 'next' for a week, like we do for usual topics.\n\nThanks.\n\nP.S. I'll be offline today (like every other Tuesday).\n"},{"id":"456526","messageId":"nycvar.QRO.7.76.6.2206021721070.349@tvgsbejvaqbjf.bet","threadId":"57907","inReplyTo":"xmqqczftx0e0.fsf@gitster.g","subject":"Re: Investigating Cirrus CI FreeBSD failures","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2022-06-02T15:22:20Z","receivedAt":"2022-06-02T15:22:53Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Junio,\n\nOn Tue, 31 May 2022, Junio C Hamano wrote:\n\n> Philippe Blain writes:\n>\n> > For now we opted to just update to 12.3, see [1].\n>\n> Indeed we did. Let's make sure we fast-track the topic down to 'master'\n> and possibly to 'maint'. I do not think it is worth letting it sit in\n> 'next' for a week, like we do for usual topics.\n\nI am very much in favor of merging this down into `maint`, as every PR run\nof GitGitGadget's PRs fails right now (and some new contributors already\nwere worried about this).\n\nThanks,\nDscho\n"}]}