qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cleber Rosa <crosa@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>, "Thomas Huth" <thuth@redhat.com>,
	"Beraldo Leal" <bleal@redhat.com>,
	"Erik Skultety" <eskultet@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Cleber Rosa" <crosa@redhat.com>,
	"Andrea Bolognani" <abologna@redhat.com>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Willian Rampazzo" <wrampazz@redhat.com>,
	"Stefan Hajnoczi" <stefanha@gmail.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Eduardo Habkost" <ehabkost@redhat.com>
Subject: [PATCH 0/2] Acceptance Tests: restore the use of target related information
Date: Thu, 25 Feb 2021 18:21:20 -0500	[thread overview]
Message-ID: <20210225232122.1254879-1-crosa@redhat.com> (raw)

This addresses two issues, restoring them to their previous behavior:

The first one, reported by Thomas Huth, a test timeout (and thus a job
failed) on CI.  The test was interrupted because of a download
timeout.  The download timeout happened due to the fact that "make
get-vm-images" is currently broken and the images matching the QEMU
targets are not being downloaded before the Avocado job.

The second one is the use of the same target related information, but
to filter out tests that don't have a matching "arch" tag.  So, if one
is not building, say "aarch64-softmmu", tests tagged with "arch:
aarch64" won't even make into the Avocado job.

For review purposes, the following job that shows the download of
ppc64le, s390x and x86_64 (but not aarch64) Fedora 31 images on a
acceptance-system-centos job:

   https://gitlab.com/cleber.gnu/qemu/-/jobs/1057043012#L63

And the following shows the download of the aarch64 Fedora 31 image
(but not any other) on a acceptance-system-ubuntu job:

   https://gitlab.com/cleber.gnu/qemu/-/jobs/1057043005#L61

Cleber Rosa (2):
  Acceptance Tests: restore downloading of VM images
  Acceptance Tests: restore filtering of tests by target arch

 tests/Makefile.include | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

-- 
2.25.4




             reply	other threads:[~2021-02-25 23:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 23:21 Cleber Rosa [this message]
2021-02-25 23:21 ` [PATCH 1/2] Acceptance Tests: restore downloading of VM images Cleber Rosa
2021-02-26  0:01   ` Philippe Mathieu-Daudé
2021-02-26 23:04     ` Cleber Rosa
2021-03-02 15:17       ` Philippe Mathieu-Daudé
2021-03-02 14:56   ` Wainer dos Santos Moschetta
2021-03-03 15:06   ` Willian Rampazzo
2021-02-25 23:21 ` [PATCH 2/2] Acceptance Tests: restore filtering of tests by target arch Cleber Rosa
2021-03-02 14:59   ` Wainer dos Santos Moschetta
2021-03-03 15:07   ` Willian Rampazzo

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=20210225232122.1254879-1-crosa@redhat.com \
    --to=crosa@redhat.com \
    --cc=abologna@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=bleal@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=eskultet@redhat.com \
    --cc=fam@euphon.net \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=thuth@redhat.com \
    --cc=wainersm@redhat.com \
    --cc=wrampazz@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).