All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Ed Maste" <emaste@freebsd.org>,
	"Beraldo Leal" <bleal@redhat.com>,
	qemu-devel@nongnu.org,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Li-Wen Hsu" <lwhsu@freebsd.org>
Subject: Re: [PATCH for-7.1] tests: Drop perl-Test-Harness from the CI containers / VMs
Date: Wed, 30 Mar 2022 09:19:28 +0100	[thread overview]
Message-ID: <YkQSkGLb6F7zB10b@redhat.com> (raw)
In-Reply-To: <20220329102808.423681-1-thuth@redhat.com>

On Tue, Mar 29, 2022 at 12:28:08PM +0200, Thomas Huth wrote:
> The perl test harness is not necessary anymore since commit 3d2f73ef75
> ("build: use "meson test" as the test harness"). Thus remove it from
> tests/lcitool/projects/qemu.yml, run "make lcitool-refresh" and manually
> clean the remaining docker / vm files that are not managed by lcitool yet.
> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  Note: This triggers a rebuild of the Centos-stream 8 container when
>  pushed to gitlab.com - which is however currently failing due to a
>  completely unrelated problem in the distro. Thus I've marked this as
>  "for-7.1" for now to avoid disturbing up our 7.0 freeze phase.

FYI The centos repo issues appear to be resolved this morning.

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 :|



  parent reply	other threads:[~2022-03-30  8:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 10:28 [PATCH for-7.1] tests: Drop perl-Test-Harness from the CI containers / VMs Thomas Huth
2022-03-29 10:39 ` Philippe Mathieu-Daudé
2022-03-30  8:19 ` Daniel P. Berrangé [this message]
2022-03-30  8:47   ` 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=YkQSkGLb6F7zB10b@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=bleal@redhat.com \
    --cc=emaste@freebsd.org \
    --cc=f4bug@amsat.org \
    --cc=lwhsu@freebsd.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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 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.