From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH OSSTEST v4] mg-all-branch-statuses: Show how up to date each branch is Date: Fri, 3 Jul 2015 14:53:00 +0100 Message-ID: <1435931580.9447.109.camel@citrix.com> References: <1435927633-10120-1-git-send-email-ian.campbell@citrix.com> <21910.37075.878736.119791@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <21910.37075.878736.119791@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Fri, 2015-07-03 at 14:40 +0100, Ian Jackson wrote: > Ian Campbell writes ("[PATCH OSSTEST v4] mg-all-branch-statuses: Show how up to date each branch is"): > > Using report_find_push_age_info allows us to provide counts of > > attempts since the last baseline on current tip as well as the first > > attempt of each of those. > > > > Since everything serialises on the repo lock I didn't bother trying to > > parallelise anything. > > Acked-by: Ian Jackson > > Do you want to provide a cron job to run this weekly, or something ? Given the "NN days" I was thinking more like daily, otherwise "NN days" is more like "+= up to 7". Where would be a good place to run it from? Is $HOME/testing.git#master always up to date after an osstest harness pass? (I think we can tolerate the occasional update under foot). Ian.