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
-- 
|: