All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Anthony PERARD <anthony.perard@citrix.com>, xen-devel@lists.xen.org
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH OSSTEST v4 3/3] Create a flight to test OpenStack with xen-unstable and libvirt
Date: Tue, 8 Dec 2015 10:23:49 +0000	[thread overview]
Message-ID: <1449570229.16124.24.camel@citrix.com> (raw)
In-Reply-To: <1448031319-3444-4-git-send-email-anthony.perard@citrix.com>

On Fri, 2015-11-20 at 14:55 +0000, Anthony PERARD wrote:

I think this will also add a devstack job to most other flights? That's a
good thing, I think.

I wonder if the flight ought to be called openstack-nova, to leave open the
possibility of other openstack-$foo flights in the future?

> Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
> 
> ---
> Change in V4:
> - also skip build-*-oldkern in make flight

Those should already be caught by cr-daily-branch
setting REVISION_LINUX_OLD=disable for all but the xen-unstable flight
(arguably that default ought to be inverted, such that make-flight by
default doesn't make such flights unless asked to, but that's not your Yakk
I think)

> - fix select_xenbranch
> - set revision_*=$REVISION_OPENSTACK_* in make-flight
>   (was revision_*=master before)
>   only REVISION_OPENSTACK_NOVA is set, the others are unset.
>   empty revision_* runvar would clone the default branch, which should
>   be master for every openstack repos

The sort of info in this last bullet would be useful in the commit message,
I think.

> diff --git a/make-flight b/make-flight
> index 8523995..5a4fc0c 100755
> --- a/make-flight
> +++ b/make-flight
> @@ -54,6 +54,12 @@ job_create_build_filter_callback () {
>          *)			return 1 ;;
>        esac
>      ;;
> +    openstack)
> +      case "$job" in
> +        *-xsm) return 1;;

I wonder, would a test-$xenarch$kern-$dom0arch-devstack-xsm be a useful
think to have though?

> +        *-oldkern) return 1;;

See above.

> diff --git a/mfi-common b/mfi-common
> index 5fbe195..f11302b 100644
> --- a/mfi-common
> +++ b/mfi-common
> @@ -59,6 +59,7 @@ xenbranch_xsm_variants () {
>      xen-4.3-testing) echo "false";;
>      xen-4.4-testing) echo "false";;
>      xen-4.5-testing) echo "false";;
> +    openstack)       echo "false";;
>      *) echo "false true";
>      esac
>  }
> @@ -102,6 +103,7 @@ create_build_jobs () {
>        rumpuserxen) continue;;
>        seabios) continue;;
>        ovmf) continue;;
> +      openstack) continue;;
>        esac
>        case "$xenbranch" in
>        xen-3.*-testing) continue;;
> @@ -127,6 +129,9 @@ create_build_jobs () {
>        "
>        ;;
>      esac
> +    if [ "$arch" = i386 ] && [ "$branch" = openstack ]; then
> +      continue

This accepts ARM, but I think you filter the test cases for that? The
filtering of build vs. test jobs in make-flight/mfi-common is a bit of a
mess, recently e21625f79d33 "make-flight: move in-lined branch vs arch
filtering into callbacks" make it a bit less bad, which might be useful to
you here?

> +    fi
>  
>      case "$arch" in
>      *)     suite=$defsuite;;

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2015-12-08 10:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 14:55 [PATCH OSSTEST v4 0/3] Have OpenStack tested on top of xen's master and libvirt's master Anthony PERARD
2015-11-20 14:55 ` [PATCH OSSTEST v4 1/3] ts-openstack-deploy: Deploy OpenStack on a host with devstack Anthony PERARD
2015-11-20 14:55 ` [PATCH OSSTEST v4 2/3] ts-openstack-tempest: Run Tempest to check OpenStack Anthony PERARD
2015-12-08 10:12   ` Ian Campbell
2015-11-20 14:55 ` [PATCH OSSTEST v4 3/3] Create a flight to test OpenStack with xen-unstable and libvirt Anthony PERARD
2015-12-08 10:23   ` Ian Campbell [this message]
2015-12-08 14:54     ` Anthony PERARD
2015-12-08 15:02       ` Ian Campbell

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=1449570229.16124.24.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=anthony.perard@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.