2005/7/18, Mark Gross <[EMAIL PROTECTED]>:
> On Friday 15 July 2005 16:14, Rik van Riel wrote:
> > On Fri, 15 Jul 2005, Mark Gross wrote:
> > > What would be wrong in expecting the folks making the driver changes
> > > have some story on how they are validating there changes don't break
> > > exist
On Friday 15 July 2005 16:14, Rik van Riel wrote:
> On Fri, 15 Jul 2005, Mark Gross wrote:
> > What would be wrong in expecting the folks making the driver changes
> > have some story on how they are validating there changes don't break
> > existing working hardware? I could probly be accomplished
Hi!
> Why can't I expect SWSusp work better and more reliable from release to
> release?
Patches welcome. Or employ someone to do swsusp development for you.
> Some possible things that could help:
>
> *Addopt a no-regressions-allowed policy and everthing stops until any
> identified regres
On Fri, 15 Jul 2005, Mark Gross wrote:
> What would be wrong in expecting the folks making the driver changes
> have some story on how they are validating there changes don't break
> existing working hardware? I could probly be accomplished in open
> source with subsystem testing volenteers.
On Fri, 15 Jul 2005, Mark Gross wrote:
On Thursday 14 July 2005 19:09, Dave Jones wrote:
On Fri, Jul 15, 2005 at 03:45:28AM +0200, Jesper Juhl wrote:
>>> The problem is the process, not than the code.
>>> * The issues are too much ad-hock code flux without enough
>>> disciplined/formal regressi
On Fri, Jul 15, 2005 at 02:47:46PM -0700, Mark Gross wrote:
> This problem is the developer making driver changes without have the
> resources
> to test the changes on a enough of the hardware effected by his change, and
> therefore probubly shouldn't be making changes they cannot realisti
On Thursday 14 July 2005 19:09, Dave Jones wrote:
> On Fri, Jul 15, 2005 at 03:45:28AM +0200, Jesper Juhl wrote:
> > > > The problem is the process, not than the code.
> > > > * The issues are too much ad-hock code flux without enough
> > > > disciplined/formal regression testing and review.
>
On Thursday 14 July 2005 19:16, Dave Airlie wrote:
> > That, of course, you cannot do. But, you can regression test a lot of
> > other things, and having a default test suite that is constantly being
> > added to and always being run before releases (that test hardware
> > agnostic stuff) could hel
On Thursday 14 July 2005 19:09, Andi Kleen wrote:
> > You can't test everything this way, nor should you, but you can test
> > many things, and adding a bit of formal testing to the release
> > procedure wouldn't be a bad thing IMO.
>
> In the linux model that's left to the distributions. In fact d
> I have always wondered how Windows got it right circa 1995 - Version after
> version, several different hardwares and it always works reliably.
> I am using Linux since 1997 and not a single time have I succeeded in getting
> it to suspend and resume reliably.
Because Windows at the time use
> That, of course, you cannot do. But, you can regression test a lot of
> other things, and having a default test suite that is constantly being
> added to and always being run before releases (that test hardware
> agnostic stuff) could help cut down on the number of regressions in
> new releases.
On Thursday 14 July 2005 20:38, Andi Kleen wrote:
> It's basically impossible to regression test swsusp except to release it.
> Its success or failure depends on exactly the driver
> combination/platform/BIOS version etc. e.g. all drivers have to cooperate
> and the particular bugs in your BIOS ne
On Thu, Jul 14, 2005 at 10:09:11PM -0400, Parag Warudkar wrote:
> I have always wondered how Windows got it right circa 1995 - Version after
> version, several different hardwares and it always works reliably.
> I am using Linux since 1997 and not a single time have I succeeded in getting
> it t
> You can't test everything this way, nor should you, but you can test
> many things, and adding a bit of formal testing to the release
> procedure wouldn't be a bad thing IMO.
In the linux model that's left to the distributions. In fact doing it properly
takes months. You wouldn't want to wait mo
On Fri, Jul 15, 2005 at 03:45:28AM +0200, Jesper Juhl wrote:
> > > The problem is the process, not than the code.
> > > * The issues are too much ad-hock code flux without enough
> > > disciplined/formal
> > > regression testing and review.
> >
> > It's basically impossible to regression
On 7/15/05, Chris Friesen <[EMAIL PROTECTED]> wrote:
> Jesper Juhl wrote:
>
> > In my oppinion it would be nice if Linus/Andrew had some basic
> > regression tests they could run on kernels before releasing them.
>
> How do you regression test behaviour on broken hardware (and BIOSes)
> that you
Jesper Juhl wrote:
In my oppinion it would be nice if Linus/Andrew had some basic
regression tests they could run on kernels before releasing them.
How do you regression test behaviour on broken hardware (and BIOSes)
that you don't have?
Chris
-
To unsubscribe from this list: send the lin
On 15 Jul 2005 02:38:58 +0200, Andi Kleen <[EMAIL PROTECTED]> wrote:
> Mark Gross <[EMAIL PROTECTED]> writes:
> >
> > The problem is the process, not than the code.
> > * The issues are too much ad-hock code flux without enough
> > disciplined/formal
> > regression testing and review.
>
> It's ba
Mark Gross <[EMAIL PROTECTED]> writes:
>
> The problem is the process, not than the code.
> * The issues are too much ad-hock code flux without enough disciplined/formal
> regression testing and review.
It's basically impossible to regression test swsusp except to release it.
Its success or f
Mark Gross <[EMAIL PROTECTED]> wrote:
>
> I know this is a broken record, but the development process within the LKML
> isn't resulting in more stable and better code. Some process change could
> be
> a good thing.
We rely upon people (such as [EMAIL PROTECTED]) to send bug reports.
> Why
I know this is a broken record, but the development process within the LKML
isn't resulting in more stable and better code. Some process change could be
a good thing.
Why does my alps mouse pad have to stop working every time I test a new
"STABLE" kernel?
Why does swsup have to start hangin
21 matches
Mail list logo
