qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] scripts: display how long each test takes to execute
Date: Mon, 12 Oct 2020 17:34:24 +0200	[thread overview]
Message-ID: <475a8cc8-9cb2-4ad0-304f-a98ec6d4993b@redhat.com> (raw)
In-Reply-To: <20201012150916.GJ39408@redhat.com>

On 12/10/20 17:09, Daniel P. Berrangé wrote:
> On Mon, Oct 12, 2020 at 05:07:18PM +0200, Thomas Huth wrote:
>> On 14/09/2020 13.09, Daniel P. Berrangé wrote:
>>> Sometimes under CI tests non-deterministically take longer to execute
>>> than expected which can trigger timeouts. It is almost impossible to
>>> diagnose this though without seeing execution time for each test case.
>>>
>>> With this change, when passing "V=1" to make, we get a duration printed
>>> at test completion:
> 
> I wasn't intending to update this given paolo's negative response to
> the patch.

FWIW I opened https://github.com/mesonbuild/meson/issues/7830 with ideas
on how to improve "meson test".  All the items I added are more or less
blockers for QEMU, but feel free to add more if you have any ideas from
your experience with Libvirt.

Paolo



      reply	other threads:[~2020-10-12 15:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14 11:09 [PATCH] scripts: display how long each test takes to execute Daniel P. Berrangé
2020-09-14 11:15 ` no-reply
2020-09-14 11:19 ` Paolo Bonzini
2020-09-14 11:33   ` Daniel P. Berrangé
2020-09-14 12:01     ` Paolo Bonzini
2020-10-12 15:07 ` Thomas Huth
2020-10-12 15:09   ` Daniel P. Berrangé
2020-10-12 15:34     ` Paolo Bonzini [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=475a8cc8-9cb2-4ad0-304f-a98ec6d4993b@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=berrange@redhat.com \
    --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).