From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: stefanha@redhat.com
Subject: [PATCH RFC 0/2] dynamic timeout for tests
Date: Tue, 7 Nov 2023 04:49:16 -0500 [thread overview]
Message-ID: <cover.1699349799.git.mst@redhat.com> (raw)
so we keep making timeouts longer for CI but one has to stop
somewhere. netdev socket test recently failed for me again
even though it's at 2 minutes already.
here's an experiment for netdev-socket.
if this works well for a while we can generalize to other
tests.
Michael S. Tsirkin (2):
osdep: add getloadavg
netdev: set timeout depending on loadavg
include/qemu/osdep.h | 10 ++++++++++
tests/qtest/netdev-socket.c | 28 +++++++++++++++++++++++++++-
meson.build | 1 +
3 files changed, 38 insertions(+), 1 deletion(-)
--
MST
next reply other threads:[~2023-11-07 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 9:49 Michael S. Tsirkin [this message]
2023-11-07 9:49 ` [PATCH RFC 1/2] osdep: add getloadavg Michael S. Tsirkin
2023-11-07 9:49 ` [PATCH RFC 2/2] netdev: set timeout depending on loadavg Michael S. Tsirkin
2023-11-07 9:57 ` [PATCH RFC 0/2] dynamic timeout for tests Philippe Mathieu-Daudé
2023-11-07 10:00 ` Michael S. Tsirkin
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=cover.1699349799.git.mst@redhat.com \
--to=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).