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. 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/
>
-
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/
This archive was generated by hypermail 2b29 : Sat Feb 15 2003 - 22:00:43 EST