libnbd | Failed pipeline for master | 2db30279
Pipeline #819889104 has failed! Project: libnbd ( https://gitlab.com/nbdkit/libnbd ) Branch: master ( https://gitlab.com/nbdkit/libnbd/-/commits/master ) Commit: 2db30279 ( https://gitlab.com/nbdkit/libnbd/-/commit/2db30279bad4f9923baa541008f5da1162... ) Commit Message: socket activation: set LISTEN_FDNAMES Add LIST... Commit Author: Laszlo Ersek ( https://gitlab.com/lersek ) Pipeline #819889104 ( https://gitlab.com/nbdkit/libnbd/-/pipelines/819889104 ) triggered by Laszlo Ersek ( https://gitlab.com/lersek ) had 1 failed job. Job #4013077739 ( https://gitlab.com/nbdkit/libnbd/-/jobs/4013077739/raw ) Stage: builds Name: x86_64-almalinux-8-clang-prebuilt-env -- You're receiving this email because of your account on gitlab.com.
On 3/28/23 08:59, GitLab wrote:
GitLab ✖ Pipeline #819889104 has failed!
Project nbdkit <https://gitlab.com/nbdkit> / libnbd <https://gitlab.com/nbdkit/libnbd> Branch master <https://gitlab.com/nbdkit/libnbd/-/commits/master>
Commit 2db30279 <https://gitlab.com/nbdkit/libnbd/-/commit/2db30279bad4f9923baa541008f5da11624d2d1f>
socket activation: set LISTEN_FDNAMES Add LIST... Commit Author Laszlo Ersek <https://gitlab.com/lersek>
Pipeline #819889104 <https://gitlab.com/nbdkit/libnbd/-/pipelines/819889104> triggered by Laszlo Ersek <https://gitlab.com/lersek>
had 1 failed job Failed job ✖ builds
x86_64-almalinux-8-clang-prebuilt-env <https://gitlab.com/nbdkit/libnbd/-/jobs/4013077739>
GitLab You're receiving this email because of your account on gitlab.com <https://gitlab.com>. Manage all notifications <https://gitlab.com/-/profile/notifications> · Help <https://gitlab.com/help>
The "copy-file-to-qcow2-compressed.sh" test case failed with: nbdkit: nbd_connect_systemd_socket_activation: recv: Connection reset by peer I started downloading a ci-almalinux-8:latest container for local repro, but meanwhile, I kicked the failed job on gitlab too, and the latter succeeded. So <https://gitlab.com/nbdkit/libnbd/-/pipelines/819889104> is green now. Laszlo
On Tue, Mar 28, 2023 at 10:01:33AM +0200, Laszlo Ersek wrote:
Pipeline #819889104 <https://gitlab.com/nbdkit/libnbd/-/pipelines/819889104> triggered by Laszlo Ersek <https://gitlab.com/lersek>
had 1 failed job Failed job ✖ builds
x86_64-almalinux-8-clang-prebuilt-env <https://gitlab.com/nbdkit/libnbd/-/jobs/4013077739>
GitLab You're receiving this email because of your account on gitlab.com <https://gitlab.com>. Manage all notifications <https://gitlab.com/-/profile/notifications> · Help <https://gitlab.com/help>
The "copy-file-to-qcow2-compressed.sh" test case failed with:
nbdkit: nbd_connect_systemd_socket_activation: recv: Connection reset by peer
I started downloading a ci-almalinux-8:latest container for local repro, but meanwhile, I kicked the failed job on gitlab too, and the latter succeeded.
So <https://gitlab.com/nbdkit/libnbd/-/pipelines/819889104> is green now.
I wonder if we have a race window in that test, perhaps a non-unique socket name? At any rate, it is transient - which is good for getting green status, but annoying for reproducing to be able to get to root cause and prevent future failures. -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
participants (3)
-
Eric Blake -
GitLab -
Laszlo Ersek