git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philippe Blain <levraiphilippeblain@gmail.com>
To: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
Cc: git@vger.kernel.org, "Ed Maste" <emaste@freebsd.org>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [PATCH] ci: update Cirrus-CI image to FreeBSD 13.0
Date: Tue, 24 May 2022 16:52:59 -0400	[thread overview]
Message-ID: <6a3aecf1-1c0d-f4fc-7d0e-455eb0ccc92c@gmail.com> (raw)
In-Reply-To: <20220524192026.2373nfcrs6bsa4ce@carlos-mbp.lan>

Hi Carlo,

Le 2022-05-24 à 15:20, Carlo Marcelo Arenas Belón a écrit :
> On Tue, May 24, 2022 at 12:58:23PM -0400, Philippe Blain wrote:
>> The FreeBSD CI build (on Cirrus-CI) has been failing in
>> 't9001-send-email.sh' for quite some time, with an error from the
>> runtime linker relating to the Perl installation:
>>
>>     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 but it fails similarly in several tests
>> in this file.
> 
> I have to admit I never tried to use cirrus, but I verified locally that a
> 12.3 version wouldn't fail as well (or so I think).
> 
> did you try to use 12.3 which should be supported for a little longer?

Yes, I tested 12.3 and it also works. We could switch to that and
keep 13.0 for later.

>  
>> The FreeBSD image we use is FreeBSD 12.2, which is unsupported since
>> March 31st, 2022 [1]. Switching to a supported version, 13.0,
>> makes this error disappear [2].
> 
> I think 13.1 might be better, since with this change we are also implicitly
> making a move to say that we don't really care about the old (but still
> supported) maintenance branch, but will only look at the "latest" version
> instead.

I agree your reasoning, but 13.1 was not listed in the list of images on Cirrus-CI [1]. They 
say they support all Google Compute Engine images, but I could not find a public list
of these images ([2] seems to be it but I don't want to create an account just
to see a list!).

> 
> still (and Ed might have a stronger opinion about it than me) either version
> would be an improvement and feel free to add my Reviewed-by for what it is
> worth.

Thanks!

> 
>>     [1] https://lore.kernel.org/git/CAPUEspgdAos4KC-3AwYDd5p+u0hGk73nGocBTFFSR7VB9+M5jw@mail.gmail.com/T/#t
> 
> this might had been mangled by your mailer, but will presume is the thread
> where I replied before, and that obviously didn't stick for these round ;)
> 

I think it's actually on your side, as the archive shows this URL
on a single line [3]. And when I hit "reply all" in Thunderbird to type this
it seems to have put in back in a single line (!)

Cheers,

Philippe.


[1] https://cirrus-ci.org/guide/FreeBSD/
[2] https://console.cloud.google.com/compute/images
[3] https://lore.kernel.org/git/20220524165823.18804-1-levraiphilippeblain@gmail.com/T/#u

  reply	other threads:[~2022-05-24 20:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24 16:58 [PATCH] ci: update Cirrus-CI image to FreeBSD 13.0 Philippe Blain
2022-05-24 19:20 ` Carlo Marcelo Arenas Belón
2022-05-24 20:52   ` Philippe Blain [this message]
2022-05-25  4:35     ` Carlo Arenas
2022-05-24 19:24 ` Ævar Arnfjörð Bjarmason
2022-05-24 20:56   ` Philippe Blain
2022-05-25 10:37 ` Johannes Schindelin
2022-05-25 12:51 ` [PATCH v2] ci: update Cirrus-CI image to FreeBSD 12.3 Philippe Blain
2022-05-25 15:50   ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6a3aecf1-1c0d-f4fc-7d0e-455eb0ccc92c@gmail.com \
    --to=levraiphilippeblain@gmail.com \
    --cc=avarab@gmail.com \
    --cc=carenas@gmail.com \
    --cc=emaste@freebsd.org \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).