From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org
Cc: Fam Zheng <fam@euphon.net>, Laurent Vivier <lvivier@redhat.com>,
Hannes Reinecke <hare@suse.com>,
qemu-block@nongnu.org, Thomas Huth <thuth@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v2 0/2] tests/qtest: Only run fuzz-tests when tested devices are available
Date: Tue, 26 Jan 2021 12:20:07 +0100 [thread overview]
Message-ID: <9fab24c7-50d7-3744-efa6-b8452d06ed4d@redhat.com> (raw)
In-Reply-To: <20210126111638.3141780-1-philmd@redhat.com>
On 1/26/21 12:16 PM, Philippe Mathieu-Daudé wrote:
> Some tests/qtest/fuzz-test fail when the device tested is
> not available in the build. Fix this by only running the
> test when devices are available.
Forgot, since v1:
- Do not make the testing generic, keep it restricted to x86 (thuth)
> FWIW Alexander Bulekov suggested an improvement, putting each
> test in a directory named by the device tested. This series
> does not cover that.
>
> Supersedes: <20210115150936.3333282-1-philmd@redhat.com>
>
> Philippe Mathieu-Daudé (2):
> tests/qtest: Only run fuzz-megasas-test if megasas device is available
> tests/qtest: Only run fuzz-virtio-scsi when virtio-scsi is available
next prev parent reply other threads:[~2021-01-26 11:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 11:16 [PATCH v2 0/2] tests/qtest: Only run fuzz-tests when tested devices are available Philippe Mathieu-Daudé
2021-01-26 11:16 ` [PATCH v2 1/2] tests/qtest: Only run fuzz-megasas-test if megasas device is available Philippe Mathieu-Daudé
2021-01-26 17:51 ` Thomas Huth
2021-01-26 18:01 ` Alexander Bulekov
2021-01-26 18:12 ` Thomas Huth
2021-01-26 11:16 ` [PATCH v2 2/2] tests/qtest: Only run fuzz-virtio-scsi when virtio-scsi " Philippe Mathieu-Daudé
2021-01-26 17:52 ` Thomas Huth
2021-01-26 11:20 ` Philippe Mathieu-Daudé [this message]
2021-01-26 11:28 ` [PATCH v2 3/2] MAINTAINERS: Cover fuzzer reproducer tests within 'Device Fuzzing' Philippe Mathieu-Daudé
2021-01-26 17:56 ` 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=9fab24c7-50d7-3744-efa6-b8452d06ed4d@redhat.com \
--to=philmd@redhat.com \
--cc=fam@euphon.net \
--cc=hare@suse.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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.