All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Kevin Wolf <kwolf@redhat.com>
Cc: John Snow <jsnow@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Qemu-block <qemu-block@nongnu.org>, Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH 0/3] iotests: Fix intermittent 030 hang
Date: Sun, 22 Mar 2020 11:16:02 +0000	[thread overview]
Message-ID: <CAFEAcA80-00Rf4c1NYyONnQ+GBh7TTj6nXarQE5u2VJn3tNW2A@mail.gmail.com> (raw)
In-Reply-To: <20200313083617.8326-1-kwolf@redhat.com>

On Fri, 13 Mar 2020 at 08:37, Kevin Wolf <kwolf@redhat.com> wrote:
>
> Peter ran into a 030 hang while testing a pull request. This turned out
> to be two bugs in the test suite at once: First was the test failing
> because a timeout was apparently too short, second was that the timeout
> would actually cause the test to hang instead of failing. This series
> should fix both.
>
> Kevin Wolf (3):
>   iotests.py: Enable faulthandler
>   python/qemu: Kill QEMU process if 'quit' doesn't work
>   iotests: Increase pause_wait() timeout
>
>  python/qemu/machine.py        | 1 +
>  tests/qemu-iotests/iotests.py | 5 ++++-
>  2 files changed, 5 insertions(+), 1 deletion(-)

Applied to master since I've been seeing this hang off-and-on.

thanks
-- PMM


      parent reply	other threads:[~2020-03-22 11:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-13  8:36 [PATCH 0/3] iotests: Fix intermittent 030 hang Kevin Wolf
2020-03-13  8:36 ` [PATCH 1/3] iotests.py: Enable faulthandler Kevin Wolf
2020-03-16 19:56   ` John Snow
2020-03-13  8:36 ` [PATCH 2/3] python/qemu: Kill QEMU process if 'quit' doesn't work Kevin Wolf
2020-03-16 19:57   ` John Snow
2020-03-20 10:15   ` Philippe Mathieu-Daudé
2020-03-13  8:36 ` [PATCH 3/3] iotests: Increase pause_wait() timeout Kevin Wolf
2020-03-16 19:58   ` John Snow
2020-03-20 10:21   ` Philippe Mathieu-Daudé
2020-03-23 18:30     ` John Snow
2020-03-20 10:12 ` [PATCH 0/3] iotests: Fix intermittent 030 hang Philippe Mathieu-Daudé
2020-03-22 11:16 ` Peter Maydell [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=CAFEAcA80-00Rf4c1NYyONnQ+GBh7TTj6nXarQE5u2VJn3tNW2A@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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.