From: Mark Peloquin <peloquin@austin.ibm.com>
To: linux-kernel@vger.kernel.org
Subject: Nightly regression run results
Date: Thu, 05 Jun 2003 11:26:49 -0500 [thread overview]
Message-ID: <3EDF6F49.8070201@austin.ibm.com> (raw)
Here are links to some 2.5.70 nightly regression comparisons:
Each -bk snapshot compared to the base:
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-bk1/2.5.70-vs-2.5.70-bk1/
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-bk2/2.5.70-vs-2.5.70-bk2/
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-bk3/2.5.70-vs-2.5.70-bk3/
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-bk4/2.5.70-vs-2.5.70-bk4/
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-bk5/2.5.70-vs-2.5.70-bk5/
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-bk6/2.5.70-vs-2.5.70-bk6/
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-bk7/2.5.70-vs-2.5.70-bk7/
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-bk8/2.5.70-vs-2.5.70-bk8/
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-bk9/2.5.70-vs-2.5.70-bk9/
Each -bk snapshot compared to the previous:
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-bk1/2.5.70-bk1-vs-2.5.70-bk2/
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-bk2/2.5.70-bk2-vs-2.5.70-bk3/
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-bk3/2.5.70-bk3-vs-2.5.70-bk4/
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-bk4/2.5.70-bk4-vs-2.5.70-bk5/
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-bk5/2.5.70-bk5-vs-2.5.70-bk6/
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-bk6/2.5.70-bk6-vs-2.5.70-bk7/
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-bk7/2.5.70-bk7-vs-2.5.70-bk8/
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-bk8/2.5.70-bk8-vs-2.5.70-bk9/
Each -mm patch compared to the base:
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-mm1/2.5.70-vs-2.5.70-mm1/
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-mm2/2.5.70-vs-2.5.70-mm2/
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-mm3/2.5.70-vs-2.5.70-mm3/
Each -mm patch compared to the previous:
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-mm2/2.5.70-mm1-vs-2.5.70-mm2/
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-mm3/2.5.70-mm2-vs-2.5.70-mm3/
Each -mjb patch compared to the base:
http://www-124.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-mjb1/2.5.70-vs-2.5.70-mjb1/
Mark
next reply other threads:[~2003-06-05 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 16:26 Mark Peloquin [this message]
2003-06-06 1:34 ` Nightly regression run results Nick Piggin
2003-06-06 22:38 ` Mark Peloquin
-- strict thread matches above, loose matches on Subject: below --
2003-06-05 18:45 Steven Pratt
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=3EDF6F49.8070201@austin.ibm.com \
--to=peloquin@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/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.