Re: [Xen-devel] [PATCH OSSTEST v2 5/6] ts-openstack-tempest: Run Tempest to check OpenStack

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Fri, 2015-09-25 at 14:04 +0100, Anthony PERARD wrote:
> > > +
> > > +sub tempest() {
> > > +  # The regex is the default one + avoid the two tests know to not work
> > > +  # which are two variations of test_volume_boot_pattern.
> > > +  target_cmd($ho, <
> > > +    $builddir/tempest/run_tempest.sh
> > 
> > Is $builddir here inherited from the previous script? I'm not sure how that
> > works?
> 
> I think the genereted $builddir end up been the same as in the previous
> script, because it's generated based on the flight name and the job name.
> Both script (ts-openstack-devstack-deploy and ts-openstack-tempest) are
> part of the same jobs.

I think all current build jobs happen to only have a single step which
actually does the build.

So I'm not sure if this is deliberate or not. Ian?

Ian.

> 
> > >  -V -- --concurrency=2
> > > '(?!.*\\[.*\\bslow\\b.*\\]|.*test_volume_boot_pattern)(^tempest\\.(ap
> > > i|sc
> > > enario|thirdparty))'
> > 
> > I think think ought to at least be in a variable with a comment
> > explaining
> > why each one is omitted.
> 
> I'll add a comment, and put this in a variable.
> 
> > It could go into a runvar, but I'm not too sure about that.
> 
> I don't see a good use of the runvar right now. But it could maybe used
> to
> bisect a single Tempest test, if that even possible. Anyway, I don't
> think
> I want to try to use a runvar for that right now.
> 
> > > +END
> > > +}
> > > +
> > > +tempest();
> 

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