All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, "Daniel P. Berrangé" <berrange@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH] tests/avocado: Remove the boot_linux.py and replay_linux.py tests
Date: Thu, 27 Feb 2025 12:18:17 +0000	[thread overview]
Message-ID: <87mse7wph2.fsf@draig.linaro.org> (raw)
In-Reply-To: <20250227110014.21048-1-thuth@redhat.com> (Thomas Huth's message of "Thu, 27 Feb 2025 12:00:14 +0100")

Thomas Huth <thuth@redhat.com> writes:

> These tests are based on the cloudinit functions from Avocado.
> The cloudinit is very, very slow compared to our other tests,
> so most of these Avocado tests have either been disabled by default
> with a decorator, or have been marked to only run with KVM.

I have no objection to dropping the boot_linux tests. However the
replay_linux tests could do with porting to use new images (the tuxrun
ones?) so we have coverage. Otherwise we only do a simple kernel boot
under replay and that covers a lot less.

Also don't forget to update MAINTAINERS.

>
> We won't include this sluggish cloudinit stuff in the functional
> framework, and we've already got plenty of other tests there that
> check pretty much the same things, so let's simply get rid of these
> old tests now.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
<snip>

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


  reply	other threads:[~2025-02-27 12:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 11:00 [PATCH] tests/avocado: Remove the boot_linux.py and replay_linux.py tests Thomas Huth
2025-02-27 12:18 ` Alex Bennée [this message]
2025-03-05  6:45   ` Thomas Huth

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=87mse7wph2.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=philmd@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.