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.xenproject.org
Subject: Re: [OSSTEST PATCH] linux-next tests: Use correct branch for baseline
Date: Thu, 20 Nov 2014 17:36:52 +0000	[thread overview]
Message-ID: <1416505012.26869.1.camel@citrix.com> (raw)
In-Reply-To: <1416491475-7078-1-git-send-email-ian.jackson@eu.citrix.com>

On Thu, 2014-11-20 at 13:51 +0000, Ian Jackson wrote:
> Make cr-daily-branch honour an environment or setting variable
> EXTRA_SGR_ARGS.  In branch-settings.linux-next set it appropriately to
> arrange that the linux-next test reports consider linux-linus tests as
> interesting as well as just linux-next ones.
> 
> (We already use a flight from linux-linus for selecting the baseline
> linux version.)
> 
> Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>

Acked-by: Ian Campbell <ian.campbell@citrix.com>

> ---
>  branch-settings.linux-next |    1 +
>  cr-daily-branch            |    2 ++
>  2 files changed, 3 insertions(+)
> 
> diff --git a/branch-settings.linux-next b/branch-settings.linux-next
> index e9bf926..1c5660b 100644
> --- a/branch-settings.linux-next
> +++ b/branch-settings.linux-next
> @@ -2,3 +2,4 @@ OSSTEST_NO_BASELINE=y
>  OSSTEST_PUSH=false
>  OLD_REVISION=determine-late
>  GITFORCEFLAG=--fail
> +EXTRA_SGR_ARGS=--branches-also=linux-linus
> diff --git a/cr-daily-branch b/cr-daily-branch
> index d00ecbb..17bb2c9 100755
> --- a/cr-daily-branch
> +++ b/cr-daily-branch
> @@ -301,6 +301,8 @@ END
>          ;;
>  esac
>  
> +sgr_args+=" $EXTRA_SGR_ARGS"
> +
>  : $flight $branch $OSSTEST_BLESSING $sgr_args
>  $DAILY_BRANCH_PREEXEC_HOOK
>  execute_flight $flight $OSSTEST_BLESSING

      reply	other threads:[~2014-11-20 17:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 13:51 [OSSTEST PATCH] linux-next tests: Use correct branch for baseline Ian Jackson
2014-11-20 17:36 ` 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=1416505012.26869.1.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.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.