From: Matthew Wilcox <willy@infradead.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: kdevops@lists.linux.dev, Chandan Babu R <chandan.babu@oracle.com>,
Amir Goldstein <amir73il@gmail.com>,
p.raghav@samsung.com,
"Pankaj Raghav (Samsung)" <kernel@pankajraghav.com>,
zlang@redhat.com, Daniel Gomez <da.gomez@samsung.com>,
Dave Chinner <david@fromorbit.com>,
djwong@kernel.org, Kent Overstreet <kent.overstreet@linux.dev>,
fstests@vger.kernel.org, gost.dev@samsung.com
Subject: Re: [PATCH kdevops] fstests: provide kconfig guidance for SOAK_DURATION
Date: Thu, 25 Jan 2024 23:24:58 +0000 [thread overview]
Message-ID: <ZbLtyg9YUyQkdFPV@casper.infradead.org> (raw)
In-Reply-To: <ZbLcXWI9bCdc9PZO@bombadil.infradead.org>
On Thu, Jan 25, 2024 at 02:10:37PM -0800, Luis Chamberlain wrote:
> The kdevops test runner has supported a custom SOAK_DURATION for
> fstests, however we were not providing any guidance. This means folks
> likely disable this. Throw a bone and provide some basic guidance and
> use 2.5 hours as the default value. There are about 46 tests today
> which use soak duration, this means if you are testing serially it
> increase total test time by about 5 days than the previously known
> total test time.
Do you have any stats on how much more effective it is to soak for 1
hour vs 5 hours vs 24 hours? Presumably there's some kind of
exponential dropoff, like 20 bugs found at 1 hour, an extra five found
by four hours and three more at 24 hours?
next prev parent reply other threads:[~2024-01-25 23:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 22:10 [PATCH kdevops] fstests: provide kconfig guidance for SOAK_DURATION Luis Chamberlain
2024-01-25 22:29 ` Darrick J. Wong
2024-01-29 20:49 ` Luis Chamberlain
2024-01-25 23:24 ` Matthew Wilcox [this message]
2024-01-29 20:57 ` Luis Chamberlain
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=ZbLtyg9YUyQkdFPV@casper.infradead.org \
--to=willy@infradead.org \
--cc=amir73il@gmail.com \
--cc=chandan.babu@oracle.com \
--cc=da.gomez@samsung.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=gost.dev@samsung.com \
--cc=kdevops@lists.linux.dev \
--cc=kent.overstreet@linux.dev \
--cc=kernel@pankajraghav.com \
--cc=mcgrof@kernel.org \
--cc=p.raghav@samsung.com \
--cc=zlang@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.