|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] Testing the kernels
Jeremy Fitzhardinge writes ("Re: [Xen-devel] Testing the kernels"):
> Regressions?
Well, not really regressions in the view of the testing system,
because the "tested" kernel tree was only just created so has all the
failures, and xen-unstable was pushed manually recently.
> > Can this be done in a way that doesn't involve waiting for you ? The
> > testing system obviously pushes automatically and it would be good to
> > publish those things in the right places without further manual
> > intervention.
>
> Yes. I was planning on setting up a cronjob on kernel.org to update the
> branch once we'd sorted out all the details.
OK. I can arrange to prod some script of yours if you prefer.
> > When we update the kernel version we intend to use, this should be a
> > fast forward update and gated though the testing in the ordinary way,
> > so it should update the same tag. Do you agree ?
>
> Hm. I was hoping at some point to have two kernels going through
> testing. We're planning on supporting 2.6.32 for a long time, so we
> should keep testing that. But I'd also like to start tracking upstream
> more closely (starting with .36) which we should also test.
OK, I guess I could have a different branch for my testing which
tracks a different branch of yours. I've called this one "linux",
as in
Subject: [linux test] 2057: tolerable FAIL - PUSHED
but perhaps I should rename it ?
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|