qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v2] tests/avocado: Remove the boot_linux.py tests
Date: Wed, 5 Mar 2025 08:08:30 +0000	[thread overview]
Message-ID: <Z8gGa72c3nwh7r-0@redhat.com> (raw)
In-Reply-To: <20250305071646.44702-1-thuth@redhat.com>

On Wed, Mar 05, 2025 at 08:16:46AM +0100, Thomas Huth wrote:
> These tests are based on the cloudinit functions from Avocado.
> The cloudinit is very, very slow compared to our other tests,
> so a lot of these Avocado tests have either been disabled by default
> with a decorator, or have been marked to only run with KVM.
> 
> 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>
> ---
>  v2: Only remove boot_linux.py, but keep replay_linux.py for now
> 
>  tests/avocado/boot_linux.py | 132 ------------------------------------
>  1 file changed, 132 deletions(-)
>  delete mode 100644 tests/avocado/boot_linux.py

Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>


With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



      reply	other threads:[~2025-03-05  8:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05  7:16 [PATCH v2] tests/avocado: Remove the boot_linux.py tests Thomas Huth
2025-03-05  8:08 ` Daniel P. Berrangé [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=Z8gGa72c3nwh7r-0@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --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 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).