7:56 a.m.
On Fri, Nov 10, 2023 at 03:38:12AM +0000, GitLab wrote:
Gitlab tried to send this to the old list, but I'm replying to the new
one (yes, I know we need to announce the new list once we are happy
that the archives are ready - that's still an ongoing task at the
moment).
If I did things right, future gitlab emails will directly target the
new address.
Pipeline #1067529654 has failed!
Project: libnbd ( https://gitlab.com/nbdkit/libnbd )
Branch: master ( https://gitlab.com/nbdkit/libnbd/-/commits/master )
Commit: 54d44263 (
https://gitlab.com/nbdkit/libnbd/-/commit/54d4426394c372413f55f648d4ad1d2... )
Commit Message: tests: Check behavior of nbd_set_strict_mode(ST...
Commit Author: Eric Blake ( https://gitlab.com/ebblake )
Pipeline #1067529654 ( https://gitlab.com/nbdkit/libnbd/-/pipelines/1067529654 )
triggered by Eric Blake ( https://gitlab.com/ebblake )
had 1 failed job.
Job #5504447391 ( https://gitlab.com/nbdkit/libnbd/-/jobs/5504447391/raw )
Stage: builds
Name: x86_64-fedora-rawhide-clang-prebuilt-env
This was a timeout in building the rust bindings on rawhide; unrelated
to my patch (which was merely adding a new unit test). Not sure why
rust timed out; it looks like timing out eats the log file that would
have let us see what the rust build was doing.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
8 a.m.
New subject: libnbd | Failed pipeline for master | 54d44263
On Fri, Nov 10, 2023 at 07:56:29AM -0600, Eric Blake wrote:
On Fri, Nov 10, 2023 at 03:38:12AM +0000, GitLab wrote:
Gitlab tried to send this to the old list, but I'm replying to the new
one (yes, I know we need to announce the new list once we are happy
that the archives are ready - that's still an ongoing task at the
moment).
If I did things right, future gitlab emails will directly target the
new address.
>
>
> Pipeline #1067529654 has failed!
>
> Project: libnbd ( https://gitlab.com/nbdkit/libnbd )
> Branch: master ( https://gitlab.com/nbdkit/libnbd/-/commits/master )
>
> Commit: 54d44263 (
https://gitlab.com/nbdkit/libnbd/-/commit/54d4426394c372413f55f648d4ad1d2... )
> Commit Message: tests: Check behavior of nbd_set_strict_mode(ST...
> Commit Author: Eric Blake ( https://gitlab.com/ebblake )
>
>
> Pipeline #1067529654 ( https://gitlab.com/nbdkit/libnbd/-/pipelines/1067529654 )
triggered by Eric Blake ( https://gitlab.com/ebblake )
> had 1 failed job.
>
> Job #5504447391 ( https://gitlab.com/nbdkit/libnbd/-/jobs/5504447391/raw )
>
> Stage: builds
> Name: x86_64-fedora-rawhide-clang-prebuilt-env
This was a timeout in building the rust bindings on rawhide; unrelated
to my patch (which was merely adding a new unit test). Not sure why
rust timed out; it looks like timing out eats the log file that would
have let us see what the rust build was doing.
I'd suggest running 'make check V=1' in the CI system so it is always
printed
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
8:12 a.m.
New subject: libnbd | Failed pipeline for master | 54d44263
On Fri, Nov 10, 2023 at 02:00:22PM +0000, Daniel P. Berrangé wrote:
> >
> > Pipeline #1067529654 ( https://gitlab.com/nbdkit/libnbd/-/pipelines/1067529654
) triggered by Eric Blake ( https://gitlab.com/ebblake )
> > had 1 failed job.
> >
> > Job #5504447391 ( https://gitlab.com/nbdkit/libnbd/-/jobs/5504447391/raw )
> >
> > Stage: builds
> > Name: x86_64-fedora-rawhide-clang-prebuilt-env
>
> This was a timeout in building the rust bindings on rawhide; unrelated
> to my patch (which was merely adding a new unit test). Not sure why
> rust timed out; it looks like timing out eats the log file that would
> have let us see what the rust build was doing.
I'd suggest running 'make check V=1' in the CI system so it is always
printed
The 'make' portion was already verbose; where we were silent was
during the 'make check' portion. Adding V=1 didn't make that more
verbose; probably something we need to tweak in our rust/run-tests.sh
script.
As it is, I just noticed that Makefile.am passes CARGO=$(CARGO) in the
TESTS_ENVIRONMENT, yet run-tests.sh hard-codes a call to 'cargo' on
$PATH instead of using ${CARGO}.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
8:14 a.m.
New subject: libnbd | Failed pipeline for master | 54d44263
On Fri, Nov 10, 2023 at 08:12:53AM -0600, Eric Blake wrote:
On Fri, Nov 10, 2023 at 02:00:22PM +0000, Daniel P. Berrangé wrote:
> > >
> > > Pipeline #1067529654 (
https://gitlab.com/nbdkit/libnbd/-/pipelines/1067529654 ) triggered by Eric Blake (
https://gitlab.com/ebblake )
> > > had 1 failed job.
> > >
> > > Job #5504447391 ( https://gitlab.com/nbdkit/libnbd/-/jobs/5504447391/raw
)
> > >
> > > Stage: builds
> > > Name: x86_64-fedora-rawhide-clang-prebuilt-env
> >
> > This was a timeout in building the rust bindings on rawhide; unrelated
> > to my patch (which was merely adding a new unit test). Not sure why
> > rust timed out; it looks like timing out eats the log file that would
> > have let us see what the rust build was doing.
>
> I'd suggest running 'make check V=1' in the CI system so it is always
> printed
The 'make' portion was already verbose; where we were silent was
during the 'make check' portion. Adding V=1 didn't make that more
verbose; probably something we need to tweak in our rust/run-tests.sh
script.
As it is, I just noticed that Makefile.am passes CARGO=$(CARGO) in the
TESTS_ENVIRONMENT, yet run-tests.sh hard-codes a call to 'cargo' on
$PATH instead of using ${CARGO}.
At any rate, it looks like the Rust timeout on rawhide is transient -
when I manually re-kicked that pipeline, it passed on the second
attempt. I'm not sure how we can go about making things less likely
to hang with transient Rust failures.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
9:39 a.m.
New subject: libnbd | Failed pipeline for master | 54d44263
On Fri, Nov 10, 2023 at 08:14:27AM -0600, Eric Blake wrote:
On Fri, Nov 10, 2023 at 08:12:53AM -0600, Eric Blake wrote:
> On Fri, Nov 10, 2023 at 02:00:22PM +0000, Daniel P. Berrangé wrote:
> > > >
> > > > Pipeline #1067529654 (
https://gitlab.com/nbdkit/libnbd/-/pipelines/1067529654 ) triggered by Eric Blake (
https://gitlab.com/ebblake )
> > > > had 1 failed job.
> > > >
> > > > Job #5504447391 (
https://gitlab.com/nbdkit/libnbd/-/jobs/5504447391/raw )
> > > >
> > > > Stage: builds
> > > > Name: x86_64-fedora-rawhide-clang-prebuilt-env
> > >
> > > This was a timeout in building the rust bindings on rawhide; unrelated
> > > to my patch (which was merely adding a new unit test). Not sure why
> > > rust timed out; it looks like timing out eats the log file that would
> > > have let us see what the rust build was doing.
> >
> > I'd suggest running 'make check V=1' in the CI system so it is
always
> > printed
>
> The 'make' portion was already verbose; where we were silent was
> during the 'make check' portion. Adding V=1 didn't make that more
> verbose; probably something we need to tweak in our rust/run-tests.sh
> script.
>
> As it is, I just noticed that Makefile.am passes CARGO=$(CARGO) in the
> TESTS_ENVIRONMENT, yet run-tests.sh hard-codes a call to 'cargo' on
> $PATH instead of using ${CARGO}.
At any rate, it looks like the Rust timeout on rawhide is transient -
when I manually re-kicked that pipeline, it passed on the second
attempt. I'm not sure how we can go about making things less likely
to hang with transient Rust failures.
We had curl timeout on in a libvirt pipeline today as well [1], I don't
think that will repeat too often. And I don't think there's much we can
do about it.
[1]
https://libvirt.gitlab.io/-/libvirt/-/jobs/5505153760/artifacts/logs/avoc...
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
_______________________________________________
Libguestfs mailing list -- guestfs(a)lists.libguestfs.org
To unsubscribe send an email to guestfs-leave(a)lists.libguestfs.org
12:54 p.m.
New subject: libnbd | Failed pipeline for master | 54d44263
On Fri, Nov 10, 2023 at 08:12:50AM -0600, Eric Blake wrote:
On Fri, Nov 10, 2023 at 02:00:22PM +0000, Daniel P. Berrangé wrote:
> > >
> > > Pipeline #1067529654 (
https://gitlab.com/nbdkit/libnbd/-/pipelines/1067529654 ) triggered by Eric Blake (
https://gitlab.com/ebblake )
> > > had 1 failed job.
> > >
> > > Job #5504447391 ( https://gitlab.com/nbdkit/libnbd/-/jobs/5504447391/raw
)
> > >
> > > Stage: builds
> > > Name: x86_64-fedora-rawhide-clang-prebuilt-env
> >
> > This was a timeout in building the rust bindings on rawhide; unrelated
> > to my patch (which was merely adding a new unit test). Not sure why
> > rust timed out; it looks like timing out eats the log file that would
> > have let us see what the rust build was doing.
>
> I'd suggest running 'make check V=1' in the CI system so it is always
> printed
The 'make' portion was already verbose; where we were silent was
during the 'make check' portion. Adding V=1 didn't make that more
verbose; probably something we need to tweak in our rust/run-tests.sh
script.
As it is, I just noticed that Makefile.am passes CARGO=$(CARGO) in the
TESTS_ENVIRONMENT, yet run-tests.sh hard-codes a call to 'cargo' on
$PATH instead of using ${CARGO}.
Any time you see that please push a fix. Unfortunately there are
places (also in tests/*.sh) where we directly call utilties where we
ought to go through the configure variable instead. This breaks some
real world systems -- macOS in particular -- so these are actual bugs.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
192
days inactive
192
days old
5 comments
4 participants
participants (4)
-
Daniel P. Berrangé -
Eric Blake -
Martin Kletzander -
Richard W.M. Jones