xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH OSSTEST 2/2] cambridge: arrange to test each new baseline
Date: Fri, 24 Jul 2015 18:07:12 +0100	[thread overview]
Message-ID: <21938.28864.754071.380388@mariner.uk.xensource.com> (raw)
In-Reply-To: <1436775392-14815-2-git-send-email-ian.campbell@citrix.com>

Ian Campbell writes ("[PATCH OSSTEST 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.
> 
> 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.
...
> +    baselines-only)
> +        #subject-prefix="[... ] "
> +        cat >> $heading <<END
> +This branch is configured for baseline tests only.

ITYM "This run is configured..." since the same "branch" may be run
either way (even if the ap-* is actually set up never to do so).

With that change,

Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>

Ian.

      reply	other threads:[~2015-07-24 17:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13  8:16 [PATCH OSSTEST 2/2] cambridge: arrange to test each new baseline Ian Campbell
2015-07-24 17:07 ` Ian Jackson [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=21938.28864.754071.380388@mariner.uk.xensource.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=ian.campbell@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 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).