From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH OSSTEST v3 2/2] cambridge: arrange to test each new baseline Date: Wed, 9 Sep 2015 17:13:00 +0100 Message-ID: <1441815180.24450.347.camel@citrix.com> References: <1439479117-4267-1-git-send-email-ian.campbell@citrix.com> <1439479117-4267-2-git-send-email-ian.campbell@citrix.com> <21964.56549.413004.947991@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <21964.56549.413004.947991@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 Thu, 2015-08-13 at 19:07 +0100, Ian Jackson wrote: > Ian Campbell writes ("[PATCH OSSTEST v3 2/2] cambridge: arrange to test > each new baseline"): > > Provide a new cr-daily-branch setting OSSTEST_BASELINES_ONLY which > > causes it to only attempt to test the current baseline (if it is > > untested) and never the tip version. Such tests will not result in any > > push. > > > > Each new baseline is tested exactly once (i.e. we aren't repeating > > hoping for a pass), hence the correct revision is just the one tested > > by the last run on the branch. > > > > Add a cronjob to Cambridge which runs in this manner, ensuring that > > there will usually be some sort of reasonably up to date baseline for > > any given branch which can be used for comparisons in adhoc testing or > > bisections. > > > > This will also give us some data on the success of various branches on > > the set of machines in Cambridge, which can be useful/interesting. > > > > Signed-off-by: Ian Campbell > > Acked-by: Ian Jackson Added both patches to pretest, thanks.