diff mbox

[OSSTEST] crontab: Drop linux-mingo-tip-master linux-next linux-linus

Message ID 1461336883-29315-1-git-send-email-ian.jackson@eu.citrix.com (mailing list archive)
State New, archived
Headers show

Commit Message

Ian Jackson April 22, 2016, 2:54 p.m. UTC
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@eu.citrix.com>
CC: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
CC: Boris Ostrovsky <boris.ostrovsky@oracle.com>
CC: David Vrabel <david.vrabel@citrix.com>
CC: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
CC: Wei Liu <wei.liu2@citrix.com>
CC: Roger Pau Monne <roger.pau@citrix.com>
CC: Juergen Gross <jgross@suse.com>
CC: Anshul Makkar <anshul.makkar@citrix.com>
---
 crontab |    5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

Comments

Roger Pau Monne April 22, 2016, 5:08 p.m. UTC | #1
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@eu.citrix.com>
> CC: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> CC: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> CC: David Vrabel <david.vrabel@citrix.com>
> CC: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> CC: Wei Liu <wei.liu2@citrix.com>
> CC: Roger Pau Monne <roger.pau@citrix.com>
> CC: Juergen Gross <jgross@suse.com>
> CC: Anshul Makkar <anshul.makkar@citrix.com>

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@citrix.com>

> ---
>  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@citrix.com,ian.campbell@eu.citrix.com
>  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.
Wei Liu April 22, 2016, 5:13 p.m. UTC | #2
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.
> 

Thanks for doing this!

Wei.
Juergen Gross April 27, 2016, 4:37 a.m. UTC | #3
On 22/04/16 19:08, Roger Pau Monne wrote:
> 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@eu.citrix.com>
>> CC: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>> CC: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>> CC: David Vrabel <david.vrabel@citrix.com>
>> CC: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>> CC: Wei Liu <wei.liu2@citrix.com>
>> CC: Roger Pau Monne <roger.pau@citrix.com>
>> CC: Juergen Gross <jgross@suse.com>
>> CC: Anshul Makkar <anshul.makkar@citrix.com>
> 
> This looks fine to me, but I think I needs to be Acked by the Linux 
> maintainers. FWIW:

Acked-by: Juergen Gross <jgross@suse.com>

> 
> Acked-by: Roger Pau Monné <roger.pau@citrix.com>
> 
>> ---
>>  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@citrix.com,ian.campbell@eu.citrix.com
>>  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.
>
Ian Jackson April 28, 2016, 4:22 p.m. UTC | #4
Juergen Gross writes ("Re: [OSSTEST PATCH] crontab: Drop linux-mingo-tip-master linux-next linux-linus"):
> On 22/04/16 19:08, Roger Pau Monne wrote:
> > This looks fine to me, but I think I needs to be Acked by the Linux 
> > maintainers. FWIW:
> 
> Acked-by: Juergen Gross <jgross@suse.com>

Thanks.  I have installed this new crontab.

Ian.
diff mbox

Patch

diff --git a/crontab b/crontab
index 2cfad74..6ddc2b8 100755
--- a/crontab
+++ b/crontab
@@ -7,10 +7,9 @@  MAILTO=ian.jackson@citrix.com,ian.campbell@eu.citrix.com
 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"
+6-59/15   	*	* * *		cd testing.git && EXTRA_BRANCHES='linux-3.0 rumpuserxen libvirt' ./cr-for-branches bisects -w "./cr-try-bisect --real"
 #8-59/5		*	* * *		cd bisects/adhoc.git &&	with-lock-ex -q data-tree-lock bash -c "./cr-try-bisect-adhoc; exit $?"
 22		8	* * *		cd testing.git && BRANCHES=maintjobs		./cr-for-branches . -w ./cr-all-branch-statuses ''
 3		4	* * *		savelog -c28 testing.git/tmp/cr-for-branches.log >/dev/null