From: Nivedita Singhvi <niv@us.ibm.com>
To: netdev@oss.sgi.com
Subject: Automated linux kernel testing results
Date: Fri, 03 Jun 2005 17:20:04 -0700 [thread overview]
Message-ID: <42A0F3B4.1060601@us.ibm.com> (raw)
For those who don't read lkml, I thought I'd point to
Martin Bligh's post regarding automated testing being
set up, since some people on this list were interested.
http://marc.theaimsgroup.com/?l=linux-kernel&m=111775021327595&w=2
Networking tests are in plan...
thanks,
Nivedita
--------------------------
OK, I've finally got this to the point where I can publish it.
http://ftp.kernel.org/pub/linux/kernel/people/mbligh/abat/regression_matrix.html
Currently it builds and boots any mainline, -mjb, -mm kernel within
about 15 minutes of release. runs dbench, tbench, kernbench, reaim and fsx.
Currently I'm using a 4x AMD64 box, a 16x NUMA-Q, 4x NUMA-Q, 32x x440
(ia32)
PPC64 Power 5 LPAR, PPC64 Power 4 LPAR, and PPC64 Power 4 bare metal
system.
The config files it uses are linked by the machine names in the column
headers.
Thanks to all the other IBM people who've worked on the ABAT test system
that this stuff relies on - too many to list, but especially Andy, Adam,
and Enrique, who have fixed endless bugs, and put up with my incessant
bitching about it all not working as it should ;-)
Clicking on the failure ones error codes should take you to somewhere
vaguely helpful to diagnose it. Clicking on the job number just below
that takes you to the info I'm publishing right now, which should
include perf results and profiles, etc. I'll add graphs, etc later,
comparing performance across kernels (I have them ... just not automated).
next reply other threads:[~2005-06-04 0:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-04 0:20 Nivedita Singhvi [this message]
2005-06-04 5:01 ` Automated linux kernel testing results Jonathan Day
2005-06-06 18:30 ` Nivedita Singhvi
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=42A0F3B4.1060601@us.ibm.com \
--to=niv@us.ibm.com \
--cc=netdev@oss.sgi.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).