From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@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: Wed, 1 Dec 2021 09:44:45 +0100 [thread overview]
Message-ID: <a809bd28-2083-5677-be41-f64bd09f617c@redhat.com> (raw)
In-Reply-To: <YaSmeFqGGFlty75h@redhat.com>
On 29/11/2021 11.07, Daniel P. Berrangé wrote:
> 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.
There haven't been any firm reasons, it's mostly simply because the distros
that I picked (Fedora and Debian) only offer the 32-bit versions here. I
used those two distros since I wanted to pick a distro with a recent Python,
and one with an older version of Python, so I first wanted to go with Fedora
and CentOS 8. But then I remembered that CentOS 8 will soon be EOL, and we
haven't decided what to do here yet (I guess we should switch to CentOS
Stream?), so I used Debian instead.
Thomas
prev parent reply other threads:[~2021-12-01 8:47 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é
2021-12-01 8:44 ` Thomas Huth [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=a809bd28-2083-5677-be41-f64bd09f617c@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=jsnow@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).