From: "Martin J. Bligh" <mbligh@mbligh.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>, Andy Whitcroft <apw@shadowen.org>,
Adam Litke <agl@us.ibm.com>, Enrique Gaona <egaona@us.ibm.com>
Subject: [ANNOUNCE] automated linux kernel testing results
Date: Thu, 02 Jun 2005 15:03:18 -0700 [thread overview]
Message-ID: <531740000.1117749798@flay> (raw)
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.
Andrew, you should be able to see build failures in -mm more easily now ;-)
I'll work on some automatic email triggers to you if you want them.
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 ;-)
It will do various other bits and pieces ... more profiling, more tests,
it'll do patches, etc as well. I don't want to push much volume up to
kernel.org (I just copy a small subset of the generated files right now),
but there are more runs queued with some fixup patches on top of -mm tree,
for example. It did also do -bk and -git nightly builds, they're not in
this matrix, but I'll add them back soon.
Andrew, if you want some other test added to the mix, please let me
know ... though theoretically we can do multi-machine tests (eg networked),
I want to stick with single-machine ones for now. There's a huge pile of
tests we intend to add ... but I thought I'd throw the general results
mechanism out there for people to look at.
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).
M.
next reply other threads:[~2005-06-02 22:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 22:03 Martin J. Bligh [this message]
2005-06-03 5:51 ` [ANNOUNCE] automated linux kernel testing results Greg KH
2005-06-03 5:45 ` Martin J. Bligh
2005-06-03 6:13 ` Greg KH
2005-06-03 13:12 ` Denis Vlasenko
2005-06-03 13:35 ` Martin J. Bligh
2005-06-07 23:00 ` Martin J. Bligh
2005-06-07 23:09 ` Jeff Garzik
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=531740000.1117749798@flay \
--to=mbligh@mbligh.org \
--cc=agl@us.ibm.com \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=egaona@us.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox