All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH v2 2/2] cambridge: arrange to test each new baseline
Date: Wed, 12 Aug 2015 16:27:13 +0100	[thread overview]
Message-ID: <1439393233.8356.53.camel@citrix.com> (raw)
In-Reply-To: <1439388539.8356.32.camel@citrix.com>

On Wed, 2015-08-12 at 15:08 +0100, Ian Campbell wrote:
> I think I need to do something with check_tested to find a flight in the
> database.

I came up with this incremental patch. I need to generate an up to date
baseline for a flight on the Cambridge infra in order to fully test all the
cases so I'm just running a linux-arm-xen flight (it doesn't change often
and only has a handful of jobs). I'll repost once that is done and I've
tested some more.

diff --git a/cr-daily-branch b/cr-daily-branch
index 4b9b525..f9edbd4 100755
--- a/cr-daily-branch
+++ b/cr-daily-branch
@@ -100,6 +100,13 @@ if [ "x$OSSTEST_BASELINES_ONLY" = xy ] ; then
     force_baseline=baselines-only
     wantpush=false
     skipidentical=true
+    if [ "x$treeurl" != xnone: ]; then
+	treearg=--tree-$tree=$treeurl
+    fi
+    tested_revision=`check_tested $treearg --print-revision=$tree`
+    if [ "x$tested_revision" != x ]; then
+	OLD_REVISION="$tested_revision"
+    fi
 elif [ "x$OSSTEST_NO_BASELINE" != xy ] ; then
 	testedflight=`check_tested --revision-$tree="$OLD_REVISION"`
 
Ian.

  reply	other threads:[~2015-08-12 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27 10:55 [PATCH v2 1/2] cr-daily-branch: Begin to support other reasons for forcing a baseline Ian Campbell
2015-07-27 10:55 ` [PATCH v2 2/2] cambridge: arrange to test each new baseline Ian Campbell
2015-08-12 14:08   ` Ian Campbell
2015-08-12 15:27     ` Ian Campbell [this message]
2015-08-12 15:46       ` Ian Jackson
2015-08-12 16:31         ` Ian Campbell
2015-08-13 10:47           ` Ian Jackson

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=1439393233.8356.53.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.