Re: [PATCH OSSTEST v4 3/3] Create a flight to test OpenStack with xen-unstable and libvirt

[Ian Campbell <ian.campbell@citrix.com>]

On Tue, 2015-12-08 at 14:54 +0000, Anthony PERARD wrote:
> On Tue, Dec 08, 2015 at 10:23:49AM +0000, Ian Campbell wrote:
> > 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.
> 
> That was not my intention. It's true that the more test, the better, but on
> the other hands it takes about 1h to deploy+test openstack, after
> installing the host.

1h isn't outsides the realms of reasonableness, but I'll let Ian comment on
available colo test bandwidth.

> 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?
> 
> Probably, that would test xsm with a different scenario.

Indeed.

In fact I wonder if we should have a general policy of defaulting to
testing with XSM turned on. After all I would expect that to find strictly
more bugs than running without.

[...]
> Yes, ARM should be filter elsewere. I'll give a look at this commit.

For both this and the question of whether the devstack is being added to
the other flights or not I would recommend running
"standalone-generate-dump-flight-runvars > before" and "s-g-d-f-r > after"
with and without your change and examining the diff.

I usually run it with eatmydata for minimum runtimes, although that has a
small chance in theory of corrupting standalone.db.

Ian.

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