qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL v2 00/13] Block layer patches
Date: Tue, 6 Aug 2024 20:43:22 +1000	[thread overview]
Message-ID: <c71e380d-883c-4f30-9629-1baad4641363@linaro.org> (raw)
In-Reply-To: <20240806080217.14941-1-kwolf@redhat.com>

On 8/6/24 18:02, Kevin Wolf wrote:
> The following changes since commit e7207a9971dd41618b407030902b0b2256deb664:
> 
>    Merge tag 'for-upstream' of https://gitlab.com/bonzini/qemu into staging (2024-08-06 08:02:34 +1000)
> 
> are available in the Git repository at:
> 
>    https://repo.or.cz/qemu/kevin.git tags/for-upstream
> 
> for you to fetch changes up to 91f16b6cdccd2942ae09d155cf3f79e6bbb485d5:
> 
>    iotests/024: exclude 'backing file format' field from the output (2024-08-06 09:54:24 +0200)
> 
> ----------------------------------------------------------------
> Block layer patches
> 
> - scsi-block: Fix error handling with r/werror=stop
> - Depend on newer clang for TSA, make WITH_GRAPH_RDLOCK_GUARD() fully
>    checked, fix block-copy to add missing lock
> - vvfat: Fix write bugs for large files and add iotests
> - Clean up blockdev-snapshot-internal-sync doc
> - Fix iotests 024 for qed


Fails testing:

https://gitlab.com/qemu-project/qemu/-/jobs/7515110500

fat16.py:308:44: E1131: unsupported operand type(s) for | (unsupported-binary-operation)
fat16.py:392:23: E1131: unsupported operand type(s) for | (unsupported-binary-operation)
fat16.py:466:42: E1131: unsupported operand type(s) for | (unsupported-binary-operation)
fat16.py:500:31: E1131: unsupported operand type(s) for | (unsupported-binary-operation)
fat16.py:500:60: E1131: unsupported operand type(s) for | (unsupported-binary-operation)


>   qapi/block-core.json               |   7 +-
>   include/block/graph-lock.h         |  21 +-
>   block/block-copy.c                 |   4 +-
>   block/vvfat.c                      |  27 +-
>   hw/scsi/scsi-disk.c                |  73 ++--
>   tests/qemu-iotests/fat16.py        | 690 +++++++++++++++++++++++++++++++++++++
>   tests/qemu-iotests/testenv.py      |   2 +-
>   meson.build                        |  14 +-
>   tests/qemu-iotests/024             |   2 +-
>   tests/qemu-iotests/024.out         |   1 -
>   tests/qemu-iotests/check           |   2 +-
>   tests/qemu-iotests/tests/vvfat     | 485 ++++++++++++++++++++++++++
>   tests/qemu-iotests/tests/vvfat.out |   5 +
>   13 files changed, 1280 insertions(+), 53 deletions(-)
>   create mode 100644 tests/qemu-iotests/fat16.py
>   create mode 100755 tests/qemu-iotests/tests/vvfat
>   create mode 100755 tests/qemu-iotests/tests/vvfat.out


r~


  reply	other threads:[~2024-08-06 10:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06  8:02 [PULL v2 00/13] Block layer patches Kevin Wolf
2024-08-06 10:43 ` Richard Henderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-05-18 11:30 Kevin Wolf
2021-05-19 20:00 ` Peter Maydell

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=c71e380d-883c-4f30-9629-1baad4641363@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).