From: Warner Losh <imp@bsdimp.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Kyle Evans" <kevans@freebsd.org>
Subject: Re: [PATCH] .gitlab-ci.d/cirrus: Drop the CI job for compiling with FreeBSD 12
Date: Wed, 19 Apr 2023 03:33:47 -0600 [thread overview]
Message-ID: <CANCZdfoL7ksbOsNJJujf_=ZXbzLdSXviFqhNdcZ3DrYhkN6trg@mail.gmail.com> (raw)
In-Reply-To: <4b9d16e8-a2cb-1c78-7d4a-cdb10adcd522@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]
On Wed, Apr 19, 2023, 12:23 AM Thomas Huth <thuth@redhat.com> wrote:
> On 18/04/2023 21.46, Warner Losh wrote:
> >
> >
> > On Tue, Apr 18, 2023 at 10:02 AM Thomas Huth <thuth@redhat.com
> > <mailto:thuth@redhat.com>> wrote:
> >
> > FreeBSD 13.0 has been released in April 2021:
> >
> > https://www.freebsd.org/releases/13.0R/announce/
> > <https://www.freebsd.org/releases/13.0R/announce/>
> >
> > According to QEMU's support policy, we stop supporting the previous
> > major release two years after the the new major release has been
> > published. So we can stop testing FreeBSD 12 in our CI now.
> >
> >
> > 13.2 was just released this week, and the FreeBSD project will be
> > dropping support for 12 by the end of the year. 14.0 is up in late
> > string / early summer.
> >
> > Signed-off-by: Thomas Huth <thuth@redhat.com <mailto:
> thuth@redhat.com>>
> >
> >
> > Reviewed-by: Warner Losh <imp@bsdimp.com <mailto:imp@bsdimp.com>>
> >
> > ---
> > We should likely also update tests/vm/freebsd ... however, FreeBSD
> 13
> > seems not to use the serial console by default anymore, so I've got
> > no clue how we could use their images now... Does anybody have any
> > suggestions?
> >
> >
> > I should look at this... It should still be using serial console by
> default...
>
> I did some more tests ... looks like both
> FreeBSD-13.2-RELEASE-amd64-disc1.iso and FreeBSD-13.2-RELEASE-amd64.qcow2
> have serial (and ssh) disabled by default - but there is a
> FreeBSD-13.2-RELEASE-amd64-BASIC-CI.raw image now that has the serial
> console (and ssh) enabled by default, so I think we could use that one for
> our CI tests.
>
I'm surprised a little by this state and will see why and see if that can't
be fixed for 14.0.
Warner
Thomas
>
>
[-- Attachment #2: Type: text/html, Size: 3336 bytes --]
prev parent reply other threads:[~2023-04-19 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 16:02 [PATCH] .gitlab-ci.d/cirrus: Drop the CI job for compiling with FreeBSD 12 Thomas Huth
2023-04-18 19:28 ` Alex Bennée
2023-04-18 19:46 ` Warner Losh
2023-04-19 6:23 ` Thomas Huth
2023-04-19 9:33 ` Warner Losh [this message]
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='CANCZdfoL7ksbOsNJJujf_=ZXbzLdSXviFqhNdcZ3DrYhkN6trg@mail.gmail.com' \
--to=imp@bsdimp.com \
--cc=alex.bennee@linaro.org \
--cc=kevans@freebsd.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).