Re: [Xen-devel] [PATCH v4] OSSTEST: introduce a raisin build test

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Ian Campbell writes ("Re: [PATCH v4] OSSTEST: introduce a raisin build test"):
> More generally this now ties everything together into one build job.

I hadn't spotted that.

I think this is very undesirable.

> Currently while bisecting osstest can try and reuse e.g. the xen job
> with a different libvirt build, which saves some time. I think this is
> an unavoidable consequence of how raisin is designed to work and we'll
> just have to suck it up.

It's not just that.  It also means that failures to build different
components all get smashed into the same test step failure.  So the
osstest reports and the information in the database will lose the
knowledge of whilch component failed to build.

> The only alternative I can see would be for raisin to have an
> "incremental" mode where it can be pointed at the results of a previous
> raisin build and build additional components based on that. I suspect
> you don't want this complexity in raisin though.

If raisin doesn't want to support building individual components based
on the outputs of previous builds, then I think we need to have
osstest continue to build things the way it currently does, at least
for the main tests.

It's fine of course to have an additional test to check that raisin
works.

Ian.

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