Re: [Xen-devel] [OSSTEST PATCH] crontab: Drop linux-mingo-tip-master linux-next linux-linus

[Roger Pau Monne <roger.pau@xxxxxxxxxx>]

On Fri, Apr 22, 2016 at 03:54:43PM +0100, Ian Jackson wrote:
> It appears that no-one is looking at the output.  These have not had a
> push to the tested output branch for at least 250 days (742 days in
> the case of linux-linus!) and the reports don't seem to be generating
> any bugfixing activity.
> 
> There is a plan to do some Xen testing in Zero-day but even if that
> doesn't lead to anything we would still be just where we are now.
> 
> So drop these to save our test bandwith for more useful work.
> 
> Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
> CC: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
> CC: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
> CC: David Vrabel <david.vrabel@xxxxxxxxxx>
> CC: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
> CC: Wei Liu <wei.liu2@xxxxxxxxxx>
> CC: Roger Pau Monne <roger.pau@xxxxxxxxxx>
> CC: Juergen Gross <jgross@xxxxxxxx>
> CC: Anshul Makkar <anshul.makkar@xxxxxxxxxx>

This looks fine to me, but I think I needs to be Acked by the Linux 
maintainers. FWIW:

Acked-by: Roger Pau Monné <roger.pau@xxxxxxxxxx>

> ---
>  crontab |    5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/crontab b/crontab
> index 2cfad74..6ddc2b8 100755
> --- a/crontab
> +++ b/crontab
> @@ -7,10 +7,9 @@ MAILTO=ian.jackson@xxxxxxxxxx,ian.campbell@xxxxxxxxxxxxx
>  49           1       * * *           cd testing.git && 
> BRANCHES_ALWAYS=xen-unstable  ./cr-for-branches branches -w 
> "./cr-daily-branch --real"
>  0            *       * * *           cd testing.git && 
> BRANCHES=xen-unstable-smoke   ./cr-for-branches branches -q 
> "./cr-daily-branch --real"
>  4-59/30              *       * * *           cd testing.git &&               
>                 ./cr-for-branches branches -q "./cr-daily-branch --real"
> -18           9       * * 1,3,5       cd testing.git && BRANCHES=linux-next   
>         ./cr-for-branches branches -w "./cr-daily-branch --real"
>  18           9       * * 3,7         cd testing.git && 
> BRANCHES=xen-unstable-coverity ./cr-for-branches branches -w 
> "./cr-daily-branch --real"
> -18           4       * * *           cd testing.git && BRANCHES='linux-linus 
> linux-mingo-tip-master linux-3.0 libvirt rumpuserxen' ./cr-for-branches 
> branches -w "./cr-daily-branch --real"
> -6-59/15      *       * * *           cd testing.git && 
> EXTRA_BRANCHES='linux-linus linux-3.0 rumpuserxen libvirt' ./cr-for-branches 
> bisects -w "./cr-try-bisect --real"
> +18           4       * * *           cd testing.git && BRANCHES='linux-3.0 
> libvirt rumpuserxen' ./cr-for-branches branches -w "./cr-daily-branch --real"

Is this linux-3.0 branch actually Linux 3.0? Should we really be testing 
that? (It's quite old TBH, and it's not even maintained upstream, oldest 
longterm is 3.2).

Roger.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel