From: Juergen Gross <jgross@suse.com>
To: Roger Pau Monne <roger.pau@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Anshul Makkar <anshul.makkar@citrix.com>,
David Vrabel <david.vrabel@citrix.com>,
xen-devel@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [OSSTEST PATCH] crontab: Drop linux-mingo-tip-master linux-next linux-linus
Date: Wed, 27 Apr 2016 06:37:30 +0200 [thread overview]
Message-ID: <5720420A.4040000@suse.com> (raw)
In-Reply-To: <20160422170822.4lc5vey4hsg2j6yk@mac>
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.
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-27 4:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 14:54 [OSSTEST PATCH] crontab: Drop linux-mingo-tip-master linux-next linux-linus Ian Jackson
2016-04-22 17:08 ` Roger Pau Monne
2016-04-27 4:37 ` Juergen Gross [this message]
2016-04-28 16:22 ` Ian Jackson
2016-04-22 17:13 ` Wei Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5720420A.4040000@suse.com \
--to=jgross@suse.com \
--cc=anshul.makkar@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=roger.pau@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).