From: Fam Zheng <fam@euphon.net>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Thomas Huth" <thuth@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Robert Foley" <robert.foley@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: [PATCH] Remove Ubuntu 18.04 support from the repository
Date: Wed, 11 May 2022 14:10:22 +0100 [thread overview]
Message-ID: <20220511131022.GA5183@fam-dell> (raw)
In-Reply-To: <CAAdtpL4oGW28-r0ZuMV9nBoZGDR5L9PYM2jsKw0Fmuwx68MWdw@mail.gmail.com>
On 2022-05-11 13:13, Philippe Mathieu-Daudé via wrote:
> +Fam
> On Wed, May 11, 2022 at 1:03 PM Thomas Huth <thuth@redhat.com> wrote:
> > On 11/05/2022 12.46, Philippe Mathieu-Daudé wrote:
> > > +Robert
> > >
> > > On Wed, May 11, 2022 at 11:30 AM Daniel P. Berrangé
> > > <berrange@redhat.com> wrote:
> > >>
> > >> On Tue, May 10, 2022 at 09:56:12PM +0200, Thomas Huth wrote:
> > >>> According to our "Supported build platforms" policy, we now do not support
> > >>> Ubuntu 18.04 anymore. Remove the related files and entries from our CI.
> > >>>
> > >>> Signed-off-by: Thomas Huth <thuth@redhat.com>
> > >>> ---
> > >>> Seems like nobody touched the 18.04-based tests/vm/ubuntu* files in a
> > >>> very long time, so I assume these are not used anymore and can completely
> > >>> be removed now.
> > >>
> > >> Or it could mean that they are working fine and so haven't needed
> > >> changes...
> > >
> > > Yes :)
> >
> > At least for me "make vm-build-ubuntu.aarch64" is only failing with ssh
> > timeouts (on my x86 laptop) ... is this really supposed to work with TCG, or
> > is this KVM (on arm hosts) only?
>
> Yes this timeout code is not working. I suppose it is tied to the TCG host perf.
> I suggested a pair of patches to increase it but back then Fam didn't accepted
> them because IIRC these VMs were used by patchew (previous to Gitlab).
> Today we have better framework for testing, so I wouldn't use this script on
> CI, but it is still valuable for manual testing.
Yes I believe these are not needed by patchew anymore.
Fam
next prev parent reply other threads:[~2022-05-11 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 19:56 [PATCH] Remove Ubuntu 18.04 support from the repository Thomas Huth
2022-05-11 9:29 ` Daniel P. Berrangé
2022-05-11 10:46 ` Philippe Mathieu-Daudé via
2022-05-11 11:03 ` Thomas Huth
2022-05-11 11:13 ` Philippe Mathieu-Daudé via
2022-05-11 11:15 ` Thomas Huth
2022-05-12 9:14 ` Philippe Mathieu-Daudé via
2022-05-12 9:21 ` Daniel P. Berrangé
2022-05-12 9:59 ` Philippe Mathieu-Daudé via
2022-05-11 13:10 ` Fam Zheng [this message]
2022-05-24 15:48 ` Alex Bennée
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=20220511131022.GA5183@fam-dell \
--to=fam@euphon.net \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=f4bug@amsat.org \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=robert.foley@linaro.org \
--cc=thuth@redhat.com \
--cc=wainersm@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).