All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
	qemu-block@nongnu.org, Hanna Reitz <hreitz@redhat.com>,
	Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v3 0/4] Improve integration of iotests in the meson test harness
Date: Thu, 24 Feb 2022 15:03:36 +0100	[thread overview]
Message-ID: <8586d924-28ca-580a-defd-cf307745be5a@redhat.com> (raw)
In-Reply-To: <20220223093840.2515281-1-thuth@redhat.com>

On 2/23/22 10:38, Thomas Huth wrote:
> This way, we can now finally get the output of failed
> tests on the console again (unless you're running meson test in verbose
> mode, where meson only puts this to the log file - for incomprehensible
> reasons),

It's a bug (introduced by yours truly, which perhaps makes it less 
incomprehensible) and there's an open pull request to fix it.

Paolo


  parent reply	other threads:[~2022-02-24 14:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23  9:38 [PATCH v3 0/4] Improve integration of iotests in the meson test harness Thomas Huth
2022-02-23  9:38 ` [PATCH v3 1/4] tests/qemu-iotests: Rework the checks and spots using GNU sed Thomas Huth
2022-02-23  9:38 ` [PATCH v3 2/4] tests/qemu-iotests/meson.build: Improve the indentation Thomas Huth
2022-02-23  9:38 ` [PATCH v3 3/4] tests/qemu-iotests: Move the bash and sanitizer checks to meson.build Thomas Huth
2022-03-21 16:14   ` Hanna Reitz
2022-02-23  9:38 ` [PATCH v3 4/4] tests: Do not treat the iotests as separate meson test target anymore Thomas Huth
2022-02-24 14:03 ` Paolo Bonzini [this message]
2022-03-21 16:14 ` [PATCH v3 0/4] Improve integration of iotests in the meson test harness Hanna Reitz
2022-03-21 17:26   ` Thomas Huth
2022-03-23 11:33     ` Hanna 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=8586d924-28ca-580a-defd-cf307745be5a@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=hreitz@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 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.