On Mon, Dec 13, 2021 at 03:17:56PM +0000, Richard W.M. Jones wrote:
On Mon, Dec 13, 2021 at 04:07:27PM +0100, Martin Kletzander wrote:
> On Mon, Dec 13, 2021 at 02:40:40PM +0000, Richard W.M. Jones wrote:
> >
> >I pushed this (commit 202d0ecad) in the hope it might fix the tests.
> >However Martin indicates that the error message might be nothing to do
> >with the Fedora version. Let's see.
> >
>
> It looks like everything went swimmingly the next time around even
> before this patch:
>
>
https://gitlab.com/nbdkit/libnbd/-/pipelines/428406657
Yes, it does look like a temporary docker pull problem.
> so it clear wasn't anything with Fedora 33, although updating to F35 is
> definitely worth doing.
Yup.
> It did not happen to be before here with the containers for libnbd. I
> guess it can happen any time if there is an issue on the remote side
> when pushing a container for example.
>
> However I am facing few issues with nbdkit CI that I am still trying to
> finish and on and off working on it. The issue there is that the tests
> time out because of all the qemu invocations, especially with TCG. I am
> trying to think about what tests to skip and maybe split the load
> between different distros.
So you can disable the libguestfs-based tests if TCG is too slow:
https://src.fedoraproject.org/rpms/nbdkit/blob/rawhide/f/nbdkit.spec#_695
We probably ought to formalise that into a configure flag, but at the
moment the above trick should be reliable because we use the same in
Fedora builds on slow arches.
Also re nbdkit CI, it turns out Windows builds were broken for a while
(I fixed it a few days ago). Would be nice to CI this!
Whuen using libvirt-ci manifest to generate gitlab config and dockerfiles,
it is pretty trivial to include mingw builds in the matrix.
Regards,
Daniel
--
|: