From: Max Reitz <mreitz@redhat.com>
To: Thomas Huth <thuth@redhat.com>, Kevin Wolf <kwolf@redhat.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH] iotests: Remove 030 from the auto group
Date: Fri, 4 Sep 2020 12:38:50 +0200 [thread overview]
Message-ID: <0c90a606-c697-332d-a3b7-12aec7c67f85@redhat.com> (raw)
In-Reply-To: <51e03521-f0b7-bf29-1ab8-9025f2f4ce94@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 809 bytes --]
On 04.09.20 12:14, Thomas Huth wrote:
> On 04/09/2020 10.25, Kevin Wolf wrote:
>> Am 04.09.2020 um 07:57 hat Thomas Huth geschrieben:
>>> Test 030 is still occasionally failing in the CI ... so for the
>>> time being, let's disable it in the "auto" group. We can add it
>>> back once it got more stable.
>>>
>>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>>
>> I would rather just disable this one test function as 030 is a pretty
>> important one that tends to catch bugs.
>
> Ok, ... should it always get disabled, or shall we try to come up with
> some magic checks so that it only gets disabled in the CI pipelines (...
> though I don't have a clue how to check for Peter's merge test
> environment...)?
I suppose we could let check-block.sh set some environment variable.
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-09-04 10:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 5:57 [PATCH] iotests: Remove 030 from the auto group Thomas Huth
2020-09-04 8:25 ` Kevin Wolf
2020-09-04 10:14 ` Thomas Huth
2020-09-04 10:37 ` Kevin Wolf
2020-09-04 10:38 ` Max Reitz [this message]
2020-09-04 11:51 ` Thomas Huth
2020-09-23 18:18 ` Alberto Garcia
2020-09-24 4:08 ` Thomas Huth
2020-09-04 8:31 ` Max Reitz
2020-09-04 8:31 ` Max Reitz
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=0c90a606-c697-332d-a3b7-12aec7c67f85@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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).