qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Thomas Huth <thuth@redhat.com>, qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] iotests: Do not run the iotests during "make check" anymore
Date: Mon, 7 Oct 2019 12:00:30 +0200	[thread overview]
Message-ID: <602a9254-43f1-887f-f661-1233068646e9@redhat.com> (raw)
In-Reply-To: <20191002142146.6124-1-thuth@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 1936 bytes --]

On 02.10.19 16:21, Thomas Huth wrote:
> Running the iotests during "make check" is causing more headaches than
> benefits for the block layer maintainers, so let's disable the iotests
> during "make check" again.
> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  tests/Makefile.include   | 2 +-
>  tests/qemu-iotests/group | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)

So the background behind this patch is that I continued to
complain/whine until I had a short open discussion with Thomas in which
he agreed to send this patch.  My points were:

(1) It doesn’t seem like people care too much about this.

(2) It isn’t very useful, because we run so few tests, and they don’t
seem to be the critical ones.

(3) In the past months, I feel like I was the single person of contact
when it comes to iotests breaking, and given the above I don’t feel like
having to act immediately on a broken make check is a good use of my
time (there’s always too much to do, so I do have to prioritize (like
everyone else)).


I’d hoped that this patch would provoke people that disagree with (1) or
(2), and potentially help me out to alleviate (3).  Or maybe provoke
nobody, in which case (1) would have been confirmed.


That didn’t quite happen, but Kevin and Peter decided to reply to my
original discussion with Thomas.

From what they’ve said I gather that (1) and (2) are wrong, and I assume
that Kevin will as the/a block maintainer have the same responsibility
as me when it comes to (3).

As such, while I can’t NAK this patch in their name, I can say that I no
longer see a need for this patch, because the reasons for why I’ve
requested it have been shown to be wrong.

I assume that Thomas actually doesn’t want to see this patch merged, and
that Kevin won’t merge it either, so I think that effectively makes this
a “passive-NAK”.

Max


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      parent reply	other threads:[~2019-10-07 10:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-02 14:21 [PATCH] iotests: Do not run the iotests during "make check" anymore Thomas Huth
2019-10-02 14:39 ` Max Reitz
2019-10-02 15:03 ` Daniel P. Berrangé
2019-10-02 15:10   ` Thomas Huth
2019-10-02 15:50     ` Max Reitz
2019-10-02 23:51       ` John Snow
2019-10-07 13:03         ` Max Reitz
2019-10-07 19:10           ` John Snow
2019-10-02 17:32   ` Alex Bennée
2019-10-02 17:46     ` Thomas Huth
2019-10-07 10:00 ` Max Reitz [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=602a9254-43f1-887f-f661-1233068646e9@redhat.com \
    --to=mreitz@redhat.com \
    --cc=kwolf@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 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).