From: "Luis R. Chamberlain" <mcgrof@kernel.org>
To: "Luis R. Chamberlain" <mcgrof@kernel.org>
Cc: Amir Goldstein <amir73il@gmail.com>,
Jeff Mahoney <jeffm@suse.com>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
xfs <linux-xfs@vger.kernel.org>,
fstests <fstests@vger.kernel.org>,
Sasha Levin <Alexander.Levin@microsoft.com>,
Sasha Levin <levinsasha928@gmail.com>,
Valentin Rothberg <valentinrothberg@gmail.com>
Subject: Re: [ANN] oscheck: wrapper for fstests check.sh - tracking and working with baselines
Date: Fri, 13 Jul 2018 10:46:20 -0700 [thread overview]
Message-ID: <20180713174620.GA12723@garbanzo.do-not-panic.com> (raw)
In-Reply-To: <20180713164420.GA3620@garbanzo.do-not-panic.com>
The other thing I forgot to mention is annotations for failure rates.
For now I'll just indicate it as a ratio ratio as as part of the ending
comment for an expunge entry. For instance I just ran into a failure
with a set of stable patches for generic/475, however after re-running
the test it succeeded. So the test does not fail always. I'd like to
annotate this.
I now have to go and re-test with the oscheck/naggy-check.sh a few
times as follows:
./naggy-check.sh -s xfs_nocrc_512 -f generic/475
This will run the test in a loop until it fails, and I can use this
as an initial failure rate hint to the tester. If I wanted to get
more accurate I could use an average of few runs with naggy-check.sh.
In practice I typically am only sure a test succeeds if it passes at
least 1000 times (one can use -c 1000 on naggy-check.sh).
I will also then have to go back to the stable kernel without patches
and verify at least one failure was visible before. This will confirm
this is indeed not a regression. Likewise I'll have to test this also
with the other sections and see if this is also observed there.
Luis
next prev parent reply other threads:[~2018-07-13 18:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 2:43 [ANN] oscheck: wrapper for fstests check.sh - tracking and working with baselines Luis R. Chamberlain
2018-07-13 8:39 ` Amir Goldstein
2018-07-13 16:44 ` Luis R. Chamberlain
2018-07-13 17:46 ` Luis R. Chamberlain [this message]
2018-07-13 20:40 ` Jeff Mahoney
2018-07-13 20:50 ` Luis R. Chamberlain
2018-07-13 21:03 ` Jeff Mahoney
2018-07-14 0:52 ` Theodore Y. Ts'o
2018-07-14 6:56 ` Eryu Guan
2018-07-13 20:51 ` Matthew Wilcox
2018-07-13 20:59 ` Luis R. Chamberlain
2018-07-14 22:21 ` Matthew Wilcox
2018-12-03 23:41 ` Luis Chamberlain
2018-12-04 11:01 ` Kent Overstreet
2019-08-16 17:34 ` 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=20180713174620.GA12723@garbanzo.do-not-panic.com \
--to=mcgrof@kernel.org \
--cc=Alexander.Levin@microsoft.com \
--cc=amir73il@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=jeffm@suse.com \
--cc=levinsasha928@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=valentinrothberg@gmail.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).