All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH OSSTEST v3 2/2] cambridge: arrange to test each new baseline
Date: Wed, 9 Sep 2015 17:13:00 +0100	[thread overview]
Message-ID: <1441815180.24450.347.camel@citrix.com> (raw)
In-Reply-To: <21964.56549.413004.947991@mariner.uk.xensource.com>

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 <ian.campbell@citrix.com>
> 
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>

Added both patches to pretest, thanks.

      reply	other threads:[~2015-09-09 16:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-13 15:18 [PATCH OSSTEST v3 1/2] cr-daily-branch: Begin to support other reasons for forcing a baseline Ian Campbell
2015-08-13 15:18 ` [PATCH OSSTEST v3 2/2] cambridge: arrange to test each new baseline Ian Campbell
2015-08-13 18:07   ` Ian Jackson
2015-09-09 16:13     ` Ian Campbell [this message]

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=1441815180.24450.347.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.