[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PULL v2 00/14] Misc patches for 2022-01-27
|
From: |
Peter Maydell |
|
Subject: |
Re: [PULL v2 00/14] Misc patches for 2022-01-27 |
|
Date: |
Thu, 3 Feb 2022 16:24:13 +0000 |
On Fri, 28 Jan 2022 at 10:18, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> The following changes since commit aeb0ae95b7f18c66158792641cb6ba0cde5789ab:
>
> Merge remote-tracking branch
> 'remotes/jsnow-gitlab/tags/python-pull-request' into staging (2022-01-22
> 12:03:22 +0000)
>
> are available in the Git repository at:
>
> https://gitlab.com/bonzini/qemu.git tags/for-upstream
>
> for you to fetch changes up to 479ca4ccd54afcd54b0163532709079233d64b97:
>
> configure: fix parameter expansion of --cross-cc-cflags options (2022-01-28
> 11:13:33 +0100)
>
> ----------------------------------------------------------------
> * configure and meson fixes
> * "meson test" switch for iotests
> * deprecation of old SGX QAPI
> * unexport InterruptStatsProviderClass-related functions
Has this switch to 'meson test' for the iotests broken the
"V=1" support for 'make check'? I find that iotest failures
now no longer print the useful information about what went wrong;
instead you just get something like:
▶ 1/1 qcow2 qsd-jobs OK
1/1 qemu:block / qemu-iotests qcow2 ERROR 243.14s exit status 1
which means we no longer are capturing enough information in
build logs to be able to diagnose failures.
thanks
-- PMM
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [PULL v2 00/14] Misc patches for 2022-01-27,
Peter Maydell <=