From: Mark Peloquin <peloquin@austin.ibm.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
linstab <linstab@osdl.org>,
ltp-results <ltp-results@lists.sourceforge.net>
Subject: BENCHMARK] 2.5.72, 2.5.72-mm1, 2.5.71, 2.5.71-bk1, 2.5.71-mjb1
Date: Wed, 18 Jun 2003 21:07:11 -0500 [thread overview]
Message-ID: <3EF11ACF.4040503@austin.ibm.com> (raw)
Nightly Regression Summary
for
2.5.72 vs 2.5.72-mm1
Benchmark Pass/Fail Improvements Regressions Results Results Summary
--------------- --------- ------------ ----------- ----------- ----------- -------
dbench.ext2 P N N 2.5.72 2.5.72-mm1 report
dbench.ext3 P Y N 2.5.72 2.5.72-mm1 report
dbench.jfs P N N 2.5.72 2.5.72-mm1 report
dbench.reiser P Y N 2.5.72 2.5.72-mm1 report
dbench.xfs P N N 2.5.72 2.5.72-mm1 report
kernbench P N N 2.5.72 2.5.72-mm1 report
lmbench P Y Y 2.5.72 2.5.72-mm1 report
rawiobench P Y Y 2.5.72 2.5.72-mm1 report
specjbb P Y Y 2.5.72 2.5.72-mm1 report
specsdet P N Y 2.5.72 2.5.72-mm1 report
tbench P Y N 2.5.72 2.5.72-mm1 report
tiobench.ext2 P Y Y 2.5.72 2.5.72-mm1 report
tiobench.ext3 P Y Y 2.5.72 2.5.72-mm1 report
tiobench.jfs P Y N 2.5.72 2.5.72-mm1 report
tiobench.reiser P Y Y 2.5.72 2.5.72-mm1 report
tiobench.xfs P Y Y 2.5.72 2.5.72-mm1 report
volanomark P N N 2.5.72 2.5.72-mm1 report
http://ltcperf.ncsa.uiuc.edu/data/2.5.72-mm1/2.5.72-vs-2.5.72-mm1/
Nightly Regression Summary
for
2.5.71 vs 2.5.72
Benchmark Pass/Fail Improvements Regressions Results Results Summary
--------------- --------- ------------ ----------- ----------- ----------- -------
dbench.ext2 P N N 2.5.71 2.5.72 report
dbench.ext3 P N Y 2.5.71 2.5.72 report
dbench.jfs P N N 2.5.71 2.5.72 report
dbench.reiser P N N 2.5.71 2.5.72 report
dbench.xfs P N N 2.5.71 2.5.72 report
kernbench P N N 2.5.71 2.5.72 report
lmbench P Y Y 2.5.71 2.5.72 report
rawiobench P Y N 2.5.71 2.5.72 report
specjbb P Y Y 2.5.71 2.5.72 report
specsdet P N N 2.5.71 2.5.72 report
tbench P Y Y 2.5.71 2.5.72 report
tiobench.ext2 P N N 2.5.71 2.5.72 report
tiobench.ext3 P Y N 2.5.71 2.5.72 report
tiobench.jfs P N N 2.5.71 2.5.72 report
tiobench.reiser P Y Y 2.5.71 2.5.72 report
tiobench.xfs P N N 2.5.71 2.5.72 report
volanomark P N N 2.5.71 2.5.72 report
http://ltcperf.ncsa.uiuc.edu/data/2.5.71/2.5.70-vs-2.5.71/
Nightly Regression Summary
for
2.5.70 vs 2.5.72
Benchmark Pass/Fail Improvements Regressions Results Results Summary
--------------- --------- ------------ ----------- ----------- ----------- -------
dbench.ext2 P Y N 2.5.70 2.5.72 report
dbench.ext3 P N Y 2.5.70 2.5.72 report
dbench.jfs P N N 2.5.70 2.5.72 report
dbench.reiser P N N 2.5.70 2.5.72 report
dbench.xfs P N N 2.5.70 2.5.72 report
kernbench P N N 2.5.70 2.5.72 report
lmbench P Y Y 2.5.70 2.5.72 report
rawiobench P Y N 2.5.70 2.5.72 report
specjbb P Y N 2.5.70 2.5.72 report
specsdet P N N 2.5.70 2.5.72 report
tbench P Y Y 2.5.70 2.5.72 report
tiobench.ext2 P N N 2.5.70 2.5.72 report
tiobench.ext3 P Y Y 2.5.70 2.5.72 report
tiobench.jfs P N Y 2.5.70 2.5.72 report
tiobench.reiser P Y Y 2.5.70 2.5.72 report
tiobench.xfs P Y N 2.5.70 2.5.72 report
volanomark P N N 2.5.70 2.5.72 report
http://ltcperf.ncsa.uiuc.edu/data/2.5.72/2.5.70-vs-2.5.72/
Nightly Regression Summary
for
2.5.71 vs 2.5.71-bk1
Benchmark Pass/Fail Improvements Regressions Results Results Summary
--------------- --------- ------------ ----------- ----------- ----------- -------
dbench.ext2 P N N 2.5.71 2.5.71-bk1 report
dbench.ext3 P N Y 2.5.71 2.5.71-bk1 report
dbench.jfs P N N 2.5.71 2.5.71-bk1 report
dbench.reiser P N N 2.5.71 2.5.71-bk1 report
dbench.xfs P Y N 2.5.71 2.5.71-bk1 report
kernbench P N N 2.5.71 2.5.71-bk1 report
lmbench P Y Y 2.5.71 2.5.71-bk1 report
rawiobench P N N 2.5.71 2.5.71-bk1 report
specjbb P Y Y 2.5.71 2.5.71-bk1 report
specsdet P N N 2.5.71 2.5.71-bk1 report
tbench P Y Y 2.5.71 2.5.71-bk1 report
tiobench.ext2 P N N 2.5.71 2.5.71-bk1 report
tiobench.ext3 P Y N 2.5.71 2.5.71-bk1 report
tiobench.jfs P N N 2.5.71 2.5.71-bk1 report
tiobench.reiser P Y Y 2.5.71 2.5.71-bk1 report
tiobench.xfs P Y N 2.5.71 2.5.71-bk1 report
volanomark P N N 2.5.71 2.5.71-bk1 report
http://ltcperf.ncsa.uiuc.edu/data/2.5.71-bk1/2.5.71-vs-2.5.71-bk1/
Nightly Regression Summary
for
2.5.71 vs 2.5.71-mjb1
Benchmark Pass/Fail Improvements Regressions Results Results Summary
--------------- --------- ------------ ----------- ----------- ----------- -------
dbench.ext2 P N Y 2.5.71 2.5.71-mjb1 report
dbench.ext3 P N Y 2.5.71 2.5.71-mjb1 report
dbench.jfs P N N 2.5.71 2.5.71-mjb1 report
dbench.reiser P Y N 2.5.71 2.5.71-mjb1 report
dbench.xfs P N N 2.5.71 2.5.71-mjb1 report
kernbench P N N 2.5.71 2.5.71-mjb1 report
lmbench P Y Y 2.5.71 2.5.71-mjb1 report
rawiobench P Y Y 2.5.71 2.5.71-mjb1 report
specjbb P Y Y 2.5.71 2.5.71-mjb1 report
specsdet P N N 2.5.71 2.5.71-mjb1 report
tbench P Y N 2.5.71 2.5.71-mjb1 report
tiobench.ext2 P Y Y 2.5.71 2.5.71-mjb1 report
tiobench.ext3 P Y Y 2.5.71 2.5.71-mjb1 report
tiobench.jfs P N Y 2.5.71 2.5.71-mjb1 report
tiobench.reiser P Y Y 2.5.71 2.5.71-mjb1 report
tiobench.xfs P Y Y 2.5.71 2.5.71-mjb1 report
volanomark P N N 2.5.71 2.5.71-mjb1 report
http://ltcperf.ncsa.uiuc.edu/data/2.5.71-mjb1/2.5.71-vs-2.5.71-mjb1/
Mark
reply other threads:[~2003-06-19 1:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3EF11ACF.4040503@austin.ibm.com \
--to=peloquin@austin.ibm.com \
--cc=linstab@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-results@lists.sourceforge.net \
/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