qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philippe.mathieu.daude@gmail.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: "Daniel P . Berrange" <berrange@redhat.com>,
	"Beraldo Leal" <bleal@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Ed Maste" <emaste@freebsd.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: Tue, 29 Mar 2022 12:39:22 +0200	[thread overview]
Message-ID: <16923125-23a2-4ac0-3919-ac78f3d9ac7e@gmail.com> (raw)
In-Reply-To: <20220329102808.423681-1-thuth@redhat.com>

On 29/3/22 12:28, 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.

Preferably splitting automatic/manual:
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>

> 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.
> 
>   .gitlab-ci.d/cirrus/freebsd-12.vars                  | 2 +-
>   .gitlab-ci.d/cirrus/freebsd-13.vars                  | 2 +-
>   .gitlab-ci.d/cirrus/macos-11.vars                    | 4 ++--
>   tests/docker/dockerfiles/alpine.docker               | 1 -
>   tests/docker/dockerfiles/centos8.docker              | 1 -
>   tests/docker/dockerfiles/debian-arm64-cross.docker   | 1 -
>   tests/docker/dockerfiles/debian-s390x-cross.docker   | 1 -
>   tests/docker/dockerfiles/debian-tricore-cross.docker | 1 -
>   tests/docker/dockerfiles/fedora-i386-cross.docker    | 1 -
>   tests/docker/dockerfiles/fedora-win32-cross.docker   | 1 -
>   tests/docker/dockerfiles/fedora-win64-cross.docker   | 1 -
>   tests/docker/dockerfiles/fedora.docker               | 1 -
>   tests/docker/dockerfiles/opensuse-leap.docker        | 1 -
>   tests/docker/dockerfiles/ubuntu1804.docker           | 1 -
>   tests/docker/dockerfiles/ubuntu2004.docker           | 1 -
>   tests/lcitool/projects/qemu.yml                      | 1 -
>   tests/vm/centos.aarch64                              | 3 +--
>   tests/vm/fedora                                      | 2 +-
>   18 files changed, 6 insertions(+), 20 deletions(-)


  reply	other threads:[~2022-03-29 10:46 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é [this message]
2022-03-30  8:19 ` Daniel P. Berrangé
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=16923125-23a2-4ac0-3919-ac78f3d9ac7e@gmail.com \
    --to=philippe.mathieu.daude@gmail.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --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 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).