From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Willian Rampazzo" <willianr@redhat.com>,
"John Snow" <jsnow@redhat.com>
Subject: Re: [PATCH] gitlab-ci.d/buildtest: Add jobs that run the device-crash-test
Date: Mon, 29 Nov 2021 10:07:52 +0000 [thread overview]
Message-ID: <YaSmeFqGGFlty75h@redhat.com> (raw)
In-Reply-To: <20211126162724.1162049-1-thuth@redhat.com>
On Fri, Nov 26, 2021 at 05:27:24PM +0100, Thomas Huth wrote:
> The device-crash-test script has been quite neglected in the past,
> so that it bit-rot quite often. Let's add CI jobs that run this
> script for at least some targets, so that this script does not
> regress that easily anymore.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> .gitlab-ci.d/buildtest.yml | 23 +++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
>
> diff --git a/.gitlab-ci.d/buildtest.yml b/.gitlab-ci.d/buildtest.yml
> index 71d0f407ad..7e1cb0b3c2 100644
> --- a/.gitlab-ci.d/buildtest.yml
> +++ b/.gitlab-ci.d/buildtest.yml
> @@ -100,6 +100,17 @@ avocado-system-debian:
> IMAGE: debian-amd64
> MAKE_CHECK_ARGS: check-avocado
>
> +crash-test-debian:
> + extends: .native_test_job_template
> + needs:
> + - job: build-system-debian
> + artifacts: true
> + variables:
> + IMAGE: debian-amd64
> + script:
> + - cd build
> + - scripts/device-crash-test -q ./qemu-system-i386
> +
> build-system-fedora:
> extends: .native_build_job_template
> needs:
> @@ -134,6 +145,18 @@ avocado-system-fedora:
> IMAGE: fedora
> MAKE_CHECK_ARGS: check-avocado
>
> +crash-test-fedora:
> + extends: .native_test_job_template
> + needs:
> + - job: build-system-fedora
> + artifacts: true
> + variables:
> + IMAGE: fedora
> + script:
> + - cd build
> + - scripts/device-crash-test -q ./qemu-system-ppc
> + - scripts/device-crash-test -q ./qemu-system-riscv32
I'm curious why you picked all the 32-bit architecture targets to test
this for, since 95% of usage these days will be on the 64-bit targets ?
I guess both 32-bit & 64-bit targets probably have the same set of
devices built mostly, but still wondering if there was a reason for
your choice.
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 :|
next prev parent reply other threads:[~2021-11-29 10:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 16:27 [PATCH] gitlab-ci.d/buildtest: Add jobs that run the device-crash-test Thomas Huth
2021-11-26 22:24 ` Philippe Mathieu-Daudé
2021-11-29 10:07 ` Daniel P. Berrangé [this message]
2021-12-01 8:44 ` 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=YaSmeFqGGFlty75h@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=jsnow@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=willianr@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).