From: Max Reitz <mreitz@redhat.com>
To: John Snow <jsnow@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-stable@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 3/4] iotests.py: rewrite run_job to be pickier
Date: Thu, 23 May 2019 14:39:03 +0200 [thread overview]
Message-ID: <1ccd5e06-7442-8767-c051-91348eed9d7a@redhat.com> (raw)
In-Reply-To: <20190510190307.17647-4-jsnow@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
On 10.05.19 21:03, John Snow wrote:
> Don't pull events out of the queue that don't belong to us;
> be choosier so that we can use this method to drive jobs that
> were launched by transactions that may have more jobs.
>
> Signed-off-by: John Snow <jsnow@redhat.com>
> ---
> tests/qemu-iotests/iotests.py | 32 +++++++++++++++-----------------
> 1 file changed, 15 insertions(+), 17 deletions(-)
There are a couple of conflicts because of concurrent patches to run_job
now. I resolved those, but then noticed that the tests 245 and 255 no
longer pass; their reference output contains events like
BLOCK_JOB_PENDING and BLOCK_JOB_COMPLETED.
I’m not sure whether we should remove those event from the output. It
feels weird to me to keep them somewhere in the back log and not show
them in tests that by design have kind of a full QMP log. On the other
hand, I see that this patch is necessary. Ideally, I think run_job
should log all events that relate to the job at hand -- but our current
event_wait() matching system doesn’t allow that.
Ideas? :-/
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-05-23 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 19:03 [Qemu-devel] [PATCH v2 0/4] blockdev-backup: don't check aio_context too early John Snow
2019-05-10 19:03 ` [Qemu-devel] [PATCH v2 1/4] " John Snow
2019-05-10 19:03 ` [Qemu-devel] [PATCH v2 2/4] iotests.py: do not use infinite waits John Snow
2019-05-10 19:03 ` [Qemu-devel] [PATCH v2 3/4] iotests.py: rewrite run_job to be pickier John Snow
2019-05-23 12:39 ` Max Reitz [this message]
2019-05-23 16:16 ` John Snow
2019-05-10 19:03 ` [Qemu-devel] [PATCH v2 4/4] iotests: add iotest 250 for testing blockdev-backup across iothread contexts John Snow
2019-05-17 11:18 ` Max Reitz
2019-05-17 18:54 ` John Snow
2019-05-17 0:15 ` [Qemu-devel] [PATCH v2 0/4] blockdev-backup: don't check aio_context too early John Snow
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=1ccd5e06-7442-8767-c051-91348eed9d7a@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 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).