[libvirt PATCH] ci: mark unstable sid containers as optional

Pavel Hrdina phrdina at redhat.com
Wed Aug 18 10:43:21 UTC 2021

On Wed, Aug 18, 2021 at 02:41:31AM -0700, Andrea Bolognani wrote:
> On Tue, Aug 17, 2021 at 02:41:48PM +0200, Ján Tomko wrote:
> >  s390x-debian-sid-container:
> > -  extends: .container_job
> > +  extends: .container_optional_job
> >    variables:
> >      NAME: debian-sid-cross-s390x
> This essentially removes coverage for these architectures in a
> permanent fashion by sweeping failures under the rug, which is not an
> acceptable way to deal with a temporary failure IMO.
> I'm working on a different solution which would retain fully coverage
> while still working around the current issues with Debian sid.

If I understand this patch correctly it will only mark building the
container optional, the libvirt build would sill be mandatory so I don't
see any issue here with coverage. We would simply reuse the latest
working container to build libvirt.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20210818/e405c8a9/attachment-0001.sig>

More information about the libvir-list mailing list