QEMU-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL v2 00/15] NBD patches through 2026-10-08
Date: Wed, 14 Oct 2026 13:07:44 -0500	[thread overview]
Message-ID: <as_CCTg5aJaWkm70@redhat.com> (raw)
In-Reply-To: <f34e4a10-6673-4d18-8e51-ce4c8f17c398@linaro.org>

On Wed, Oct 14, 2026 at 10:02:46AM +0200, Richard Henderson wrote:
> On 10/12/26 23:29, Eric Blake wrote:
> > The following changes since commit 615ece3c406b262996e569f29ea6eed0d81c4d8d:
> > 
> >    Merge tag 'for-upstream' ofhttps://gitlab.com/bonzini/qemu into staging (2026-10-09 15:49:53 +0200)
> > 
> > are available in the Git repository at:
> > 
> >    https://gitlab.com/ebblake/qemu.git tags/pull-nbd-2026-10-08-v2
> > 
> > for you to fetch changes up to 3d794bcd554c3dc196685faf382fdffe7243e674:
> > 
> >    iotests/iothreads-nbd-export: Skip on s390 (2026-10-12 16:23:50 -0500)
> > 
> > [v2: sending only the updated cover letter and patch 2/15]
> > 
> > ----------------------------------------------------------------
> > NBD patches through 2026-10-08
> > 
> > Several fixes, including:
> > - Eric Blake: Update MAINTAINERS, support qemu-nbd -s -l
> > - Fiona Ebner: Report flush error on qemu-img convert
> > - Guillaume Vinke: Fix NBD client on dead connection
> > - Denis V. Lunev: Fix postcopy dirty bitmap migration
> > - Eric Farman: Several iotest improvements
> 
> This still has 13 job failures, including check-python-minreqs.
> 
> https://gitlab.com/qemu-project/qemu/-/pipelines/2945631627

Looks like most of the failures were due to the later runners being
canceled after the early failure of the check-python-minreqs syntax
check failure. At any rate, I figured out how to patch that one and
will be posting v3 shortly.

-------------------
************* Module tests.migrate-bitmaps-postcopy-test
tests/migrate-bitmaps-postcopy-test:146:8: W0201: Attribute 'drive1_sha256' defined outside __init__ (attribute-defined-outside-init)

Fixed by:
diff --git a/tests/qemu-iotests/tests/migrate-bitmaps-postcopy-test b/tests/qemu-iotests/tests/migrate-bitmaps-postcopy-test
index bada325e017..53f7dafc79a 100755
--- a/tests/qemu-iotests/tests/migrate-bitmaps-postcopy-test
+++ b/tests/qemu-iotests/tests/migrate-bitmaps-postcopy-test
@@ -115,6 +115,7 @@ class TestDirtyBitmapPostcopyMigration(iotests.QMPTestCase):
                                                           'discard=unmap')
         self.vm_b = iotests.VM(path_suffix='b').add_drive(disk_b,
                                                           'discard=unmap')
+        self.drive1_sha256 = ""
         # A bitmap on a second node makes postcopy switch nodes after setup
         self.vm_a.add_drive(disk_a1)
         self.vm_b.add_drive(disk_b1)


-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization:  qemu.org | libguestfs.org



      reply	other threads:[~2026-10-14 18:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12 21:29 [PULL v2 00/15] NBD patches through 2026-10-08 Eric Blake
2026-10-12 21:29 ` [PULL v2 02/15] qemu-nbd: Support -s and -l at the same time Eric Blake
2026-10-14  8:02 ` [PULL v2 00/15] NBD patches through 2026-10-08 Richard Henderson
2026-10-14 18:07   ` 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=as_CCTg5aJaWkm70@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox