From: Edesio Costa e Silva <edesio@softaplic.com.br>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@transmeta.com>,
lkml <linux-kernel@vger.kernel.org>,
Edesio Costa e Silva <edesio@task.com.br>
Subject: Re: 2.5.60 cheerleading...
Date: Wed, 12 Feb 2003 17:33:00 -0200 [thread overview]
Message-ID: <20030212173300.A31055@master.softaplic.com.br> (raw)
In-Reply-To: <1045075415.22295.46.camel@plars>; from plars@linuxtestproject.org on Wed, Feb 12, 2003 at 12:43:34PM -0600
On Wed, Feb 12, 2003 at 12:43:34PM -0600, Paul Larson wrote:
> This brings up an interesting point. It seems like it's very common to
> have a release that doesn't boot, or produces immediately obvious
> problems. I'm curious if you do any testing (LTP or otherwise) on the
> kernels you intend to release.
In the words of our fearless leader:
"regression testing"? What's that? If it compiles, it is good,
if it boots up it is perfect.
:-)
> If not, would it be possible for someone
> to do this? I know we could never catch every problem, but at least the
> annoying, immediately noticeable problems could be caught and fixed
> quickly.
>
> If you wanted to do this, I think that would be great. If you don't
> have time, I understand but would you be ok with me or anyone else doing
> at least a quick sniff test before release? It doesn't have to be
> anything fancy or time consuming. I'm not looking to add delays, just a
> small amount of extra testing before release so that hopefully more
> people will be willing to try the releases on their systems.
>
> Thanks,
> Paul Larson
>
> On Wed, 2003-02-12 at 09:52, Jeff Garzik wrote:
> > Just to counteract all the 2.5.60 bug reports...
> >
> > After the akpm wave of compile fixes, I booted 2.5.60-BK on my Wal-Mart
> > PC [via epia], and ran LTP on it, while also stressing it using
> > fsx-linux in another window. The LTP run showed a few minor failures,
> > but overall 2.5.60-BK is surviving just fine, and with no corruption.
> >
> > So, it's working great for me :)
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
>
>
--
Grief can take care of itself, but to get the full value of a joy you must
have somebody to divide it with. -- Mark Twain
next prev parent reply other threads:[~2003-02-12 19:22 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 15:52 2.5.60 cheerleading Jeff Garzik
2003-02-12 16:00 ` Paul Larson
2003-02-12 16:09 ` Jeff Garzik
2003-02-12 18:07 ` Dave Jones
2003-02-12 18:44 ` John Bradford
2003-02-12 18:17 ` Scott Robert Ladd
2003-02-12 18:41 ` John Bradford
2003-02-12 18:55 ` Dave Jones
2003-02-12 18:43 ` Paul Larson
2003-02-12 19:33 ` Edesio Costa e Silva [this message]
2003-02-13 15:29 ` Paul Larson
2003-02-13 15:54 ` Jörn Engel
2003-02-13 16:03 ` Dave Jones
2003-02-13 16:55 ` Paul Larson
2003-02-13 17:11 ` John Bradford
2003-02-13 18:04 ` Paul Larson
2003-02-13 18:23 ` John Bradford
2003-02-13 21:16 ` Paul Larson
2003-02-13 21:38 ` Jeff Garzik
2003-02-13 21:54 ` John Bradford
2003-02-13 21:57 ` Paul Larson
2003-02-13 22:11 ` John Bradford
2003-02-13 22:20 ` Valdis.Kletnieks
2003-02-13 22:39 ` Paul Larson
2003-02-13 22:43 ` Randy.Dunlap
2003-02-13 22:53 ` Paul Larson
2003-02-13 22:58 ` John Bradford
2003-02-14 6:36 ` Paul Larson
2003-02-20 22:29 ` Timothy D. Witham
2003-02-20 22:42 ` Jeff Garzik
2003-02-20 22:46 ` Timothy D. Witham
2003-02-14 1:21 ` Martin J. Bligh
2003-02-14 1:32 ` Linus Torvalds
2003-02-14 3:24 ` Mike Dresser
2003-02-14 9:08 ` John Bradford
2003-02-14 4:10 ` Werner Almesberger
2003-02-13 17:06 ` 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=20030212173300.A31055@master.softaplic.com.br \
--to=edesio@softaplic.com.br \
--cc=edesio@ieee.org \
--cc=edesio@task.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 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.