From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, "Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [PULL v2 for 8.0 00/35] various fixes (testing, plugins, gitdm)
Date: Wed, 22 Mar 2023 21:54:30 +0000 [thread overview]
Message-ID: <87355w5u55.fsf@linaro.org> (raw)
In-Reply-To: <CAFEAcA8ipWKpv09pyQWNQBiUhd2JYM=sn4qv2YBen-pN3beU0Q@mail.gmail.com>
Peter Maydell <peter.maydell@linaro.org> writes:
> On Wed, 22 Mar 2023 at 16:33, Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>> The following changes since commit c283ff89d11ff123efc9af49128ef58511f73012:
>>
>> Update version for v8.0.0-rc1 release (2023-03-21 17:15:43 +0000)
>>
>> are available in the Git repository at:
>>
>> https://gitlab.com/stsquad/qemu.git tags/pull-for-8.0-220323-1
>>
>> for you to fetch changes up to e35b9a2e81ccce86db6f1417b1d73bb97d7cbc17:
>>
>> qtests: avoid printing comments before g_test_init() (2023-03-22
>> 15:08:26 +0000)
>>
>> Note you will need to remove the old openbsd disk image to trigger a
>> rebuild that avoids the issues with -ENOSPC. My pipeline can be seen
>> here:
>>
>> https://gitlab.com/stsquad/qemu/-/pipelines/814624909
>>
>> ----------------------------------------------------------------
>> Misc fixes for 8.0 (testing, plugins, gitdm)
>>
>> - update Alpine image used for testing images
>> - include libslirp in custom runner build env
>> - update gitlab-runner recipe for CentOS
>> - update docker calls for better caching behaviour
>> - document some plugin callbacks
>> - don't use tags to define drives for lkft baseline tests
>> - fix missing clear of plugin_mem_cbs
>> - fix iotests to report individual results
>> - update the gitdm metadata for contributors
>> - avoid printing comments before g_test_init()
>> - probe for multiprocess support before running avocado test
>> - refactor igb.py into netdev-ethtool.py avocado test
>> - rebuild openbsd to have more space space for iotests
>
> I saw this on ppc64. I suspect it of being a pre-existing
> intermittent -- I'm retrying it.
On what platform is that?
>
> ▶ 737/761 qcow2 copy-before-write
> FAIL
> 737/761 qemu:block / io-qcow2-copy-before-write
> ERROR 6.80s exit status 1
> ――――――――――――――――――――――――――――――――――――― ✀ ―――――――――――――――――――――――――――――――――――――
> stderr:
> --- /home/pm215/qemu/tests/qemu-iotests/tests/copy-before-write.out
> +++ /home/pm215/qemu/build/all/scratch/qcow2-file-copy-before-write/copy-before-write.out.bad
> @@ -1,5 +1,21 @@
> -....
> +..F.
> +======================================================================
> +FAIL: test_timeout_break_guest (__main__.TestCbwError.test_timeout_break_guest)
> +----------------------------------------------------------------------
> +Traceback (most recent call last):
> + File "/home/pm215/qemu/tests/qemu-iotests/tests/copy-before-write",
> line 200, in test_timeout_break_guest
> + self.assertEqual(log, """\
> +AssertionError: 'wrot[90 chars])\nwrote 524288/524288 bytes at offset
> 524288\[151 chars]c)\n' != 'wrot[90 chars])\nwrite failed: Connection
> timed out\nread 10[85 chars]c)\n'
> + wrote 524288/524288 bytes at offset 0
> + 512 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> ++ write failed: Connection timed out
> +- wrote 524288/524288 bytes at offset 524288
> +- 512 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> + read 1048576/1048576 bytes at offset 0
> + 1 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> +
> +
> ----------------------------------------------------------------------
> Ran 4 tests
>
> -OK
> +FAILED (failures=1)
>
> -- PMM
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2023-03-22 23:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 16:33 [PULL v2 for 8.0 00/35] various fixes (testing, plugins, gitdm) Alex Bennée
2023-03-22 20:18 ` Peter Maydell
2023-03-22 21:54 ` Alex Bennée [this message]
2023-03-22 22:10 ` 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=87355w5u55.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=peter.maydell@linaro.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 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.