From: Eric Blake <eblake@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [PULL v3 00/15] NBD patches through 2026-10-08
Date: Thu, 15 Oct 2026 09:41:34 -0500 [thread overview]
Message-ID: <atDlexx5t7UXUqZ6@redhat.com> (raw)
In-Reply-To: <CAFXwXrnm0aNhfwfMXLe6DnM31Z7MKX7h=6UiVNusyVkZC8nGDw@mail.gmail.com>
On Thu, Oct 15, 2026 at 10:53:39AM +0200, Richard Henderson wrote:
> https://gitlab.com/qemu-project/qemu/-/pipelines/2949515618
>
> Still 8 job failures, and this time they're clearly nbd related. Did you
> not see these when testing yourself? Or is it a quirk of our k8s ci setup
> for merge testing?
Both 'make check' and 'cd build/tests/qemu-iotests; ./check -nbd' are
passing for me, but since k8s seems to be tickling something I didn't
see locally, I'll continue investigating.
Is there an easier way for me to run the CI tests on my own branch
without sending a pull request, so that I can see the same job
failures without having to cost your time first?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization: qemu.org | libguestfs.org
prev parent reply other threads:[~2026-10-15 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 18:42 [PULL v3 00/15] NBD patches through 2026-10-08 Eric Blake
2026-10-14 18:42 ` [PULL v3 11/15] iotests/migrate-bitmaps-postcopy-test: add a bitmap on a second node Eric Blake
2026-10-15 8:53 ` [PULL v3 00/15] NBD patches through 2026-10-08 Richard Henderson
2026-10-15 14:41 ` Eric Blake [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=atDlexx5t7UXUqZ6@redhat.com \
--to=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.