Re: Hard freeze with 2.6.10-rc3 and QoS, worked fine with 2.6.9
From: Thomas Graf
Date: Wed Dec 08 2004 - 12:31:46 EST
* jamal <1102518304.1023.6.camel@xxxxxxxxxxxxxxxx> 2004-12-08 10:05
> On Wed, 2004-12-08 at 09:32, Thomas Graf wrote:
> > I've put together a small testsuite allowing to easly run tests for
> > multiple versions of iproute2. It can be found at:
> > http://people.suug.ch/~tgr/iproute2/tc-testsuite.tar.gz
> Good stuff. Hopefully we can run these tests everytime we make changes
> going forward. We cant compromise quality by handwaving on instinct.
> Famous last words: "that couldnt have possibly caused a bug down there".
> I will take a look at what you have and integrate my 20-30 testcases if
> they are not covered over time - or may be adpat what you have to follow
> how i do things or maybe i can send them to you and you can integrate
I've only put a small cbq test case and the policer test in there for
now. I'd be happy to integrate your test cases if you send them to me.
I wil add more tests in the next days given time.
Our sysadmin had some cycles and set up a UML capable of booting
any kernel image by script so we can easly test all changes to iproute2
or the kernel on as many branches as we want. I've put in the latest
2.4/2.6 main releases, the latest bk snapshots of both and earlier releases
of both to ensure we keep some backward compatibility. All 2.6 branches
have 2 configs, one with action code and the other with the old policer.
I'm not quite sure which versions of iproute2 are being used by the
distributions so I've put the latest bk version and the ones of red hat,
suse and debian into it.
That's 36 kernel<->iproute2 combinations per test, given we add a few
dozen tests makes it hard to tell if something went wrong. I'll
probably need to add some more logic to it besides just checking if
the test script has written anything to stderr.
I'll be happy to put patches into the test cycle once they're posted
to netdev or alternatively add dave's bk tree to the list of branches
whichever is more reasonable.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/