Reviving an old thread from the archives... comments in-line.
> On Fri, 2010-03-26 at 12:21 -0400, caiqian at redhat.com wrote:
> > Great news! Thanks for the efforts!
> > > * What hardware will be added?
> > For the starter of the kernel testing, we definitely need some bare-metal systems for all archs that Fedora supports, and VT systems that we can perform virt-related testing.
> > > * What tests to deploy?
> > We would like to move more kernel tests to Fedora as much as possible. Most are general purpose kernel testing without too much enterprise hardware dependency. For example,
> > * KernelTier1 and KernelTier2 tests.
> > * kdump tests.
> > * perhaps hardware cert v7 tests.
> > * LTP
> Would it make sense to document  what these tests do? Just so when
> people ask, "what is kernel tier1?" ... we can direct them to the wiki
> describing the tests.
Very good point James. All tasks should be properly documented. Also,
are these tests even available for use outside of Red Hat? where are
the sources? poke poke :)
Chris Ward <cward(a)redhat.com>
Quality Engineering - Third-Party Test Coordinator
Brno, Czech Republic
Red Hat, Inc
Tel: +420 532 294 111 EXT 8262071
" Talk does not cook rice." - Chinese proverb
" The middle of every successful project
looks like a disaster." - Rosabeth Moss
" The winds of change are always near." -me
" What's the point of taking metrics, if
they are not reported?" - ISTQB
Just a heads up that I switched to using tito for tagging and building
new beaker releases.
This makes things much easier now. For example, to build a test release:
tito build --test --srpm --dist .el5
When ready for a new release I simply do:
This pulls in all the git commits since the last tag and parses them
into rpm spec changelog friendly format. (So please give descriptive
Finally to build the latest tagged release:
tito build --srpm --dist .el5
tito build --rpm
No need to modify the spec file for test builds or changelog entries.
Let me know if you have any questions.