From: Paul Larson <plars@austin.ibm.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Announce: daily 2.5 BK snapshots
Date: 09 Aug 2002 09:36:17 -0500 [thread overview]
Message-ID: <1028903778.19435.348.camel@plars.austin.ibm.com> (raw)
In-Reply-To: <3D52D1C9.9070404@mandrakesoft.com>
I probably won't be using this since my scripts already do a nightly
pull, but I'd also like to see what people think of this. I have a
setup that does a nightly pull of 2.5, builds it for UP and SMP, pushes
to two machines (UP and SMP) and runs LTP on it. Then sends me back the
results of all of it. Of course if something fails that didn't fail the
previous day, I have a limited set of Changesets as culprits so it's
easier for me to find the cause of problems when I do more frequent
testing like this. Any major problems are reported immediatly of
course, but would anyone be interested in seeing the results of this
more often? I don't know if I have enough space on the LTP website to
post all the data that's gathered every single day (It would add up
REALLY fast), but would a weekly rollup to lkml be something people
would like to see?
Thanks,
Paul Larson
next prev parent reply other threads:[~2002-08-09 14:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 19:52 Jeff Garzik
2002-08-08 19:55 ` Jeff Garzik
2002-08-08 20:04 ` Rik van Riel
2002-08-08 20:17 ` Jeff Garzik
2002-08-09 14:36 ` Paul Larson [this message]
2002-08-09 14:55 ` Larry McVoy
2002-08-09 15:19 ` Martin J. Bligh
2002-08-09 15:49 ` Larry McVoy
2002-08-09 19:03 ` Paul Larson
[not found] ` <200208082127.OAA08172@cesium.transmeta.com>
2002-08-08 21:34 ` 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=1028903778.19435.348.camel@plars.austin.ibm.com \
--to=plars@austin.ibm.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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
all inboxes | Powered by JetHome®