Re: [Xen-devel] [OSSTEST PATCH v13 21/24] Create a flight to test OpenStack with xen-unstable and libvirt

[Ian Jackson <ian.jackson@xxxxxxxxxxxxx>]

Anthony PERARD writes ("[OSSTEST PATCH v13 21/24] Create a flight to test 
OpenStack with xen-unstable and libvirt"):
> This patch creates a flight "openstack*", with those jobs:

Do you mean it creates a "branch" ?  But I don't think it does.  I
predict no changes to the output of mg-list-all-branches.  You
probably want to edit cr-for-branches.

>   build-amd64
>   build-amd64-libvirt
>   build-amd64-pvops
>   build-amd64-xsm
>   build-arm64
>   build-arm64-libvirt
>   build-arm64-pvops
>   build-arm64-xsm
>   build-armhf
>   build-armhf-libvirt
>   build-armhf-pvops
>   build-armhf-xsm
>   test-amd64-amd64-devstack
>   test-amd64-amd64-devstack-xsm
>   test-arm64-arm64-devstack
>   test-arm64-arm64-devstack-xsm
>   test-armhf-armhf-devstack
>   test-armhf-armhf-devstack-xsm

Does it add these jobs to existing flights ?  I think it probably
does.  Is that intentional ?  I think it probably isn't.  If it is you
should explain it in the commit message - and also explain why this is
OK despite you not keeping tested versions of all the input branches
(ie, risking uncontrolled regressions in openstack components breaking
the xen pushes...)

You can see what it does with standalone-dump-all-flight-runvars
(which is best run with eatmydata).

Ian.

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