[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-commits] [qemu/qemu] eea9f7: q800: move dp8393x_prom memory region
|
From: |
Peter Maydell |
|
Subject: |
[Qemu-commits] [qemu/qemu] eea9f7: q800: move dp8393x_prom memory region to Q800Machi... |
|
Date: |
Fri, 12 Jan 2024 09:28:00 -0800 |
Branch: refs/heads/master
Home: https://github.com/qemu/qemu
Commit: eea9f763002b369c2d601a3eedb905b945563e5a
https://github.com/qemu/qemu/commit/eea9f763002b369c2d601a3eedb905b945563e5a
Author: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Date: 2024-01-11 (Thu, 11 Jan 2024)
Changed paths:
M hw/m68k/q800.c
M include/hw/m68k/q800.h
Log Message:
-----------
q800: move dp8393x_prom memory region to Q800MachineState
There is no need to dynamically allocate the memory region from the heap.
Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Message-ID: <20231227210212.245106-1-mark.cave-ayland@ilande.co.uk>
Reviewed-by: Thomas Huth <huth@tuxfamily.org>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Laurent Vivier <laurent@vivier.eu>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: b01932889d62f20b5d1eedd605a5ccc4fe73004f
https://github.com/qemu/qemu/commit/b01932889d62f20b5d1eedd605a5ccc4fe73004f
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: 2024-01-11 (Thu, 11 Jan 2024)
Changed paths:
M tests/qtest/virtio-net-failover.c
Log Message:
-----------
qtest: use correct boolean type for failover property
QMP device_add does not historically validate the parameter types.
At some point it will likely change to enforce correct types, to
match behaviour of -device. The failover property is expected to
be a boolean in JSON.
Signed-off-by: "Daniel P. Berrangé" <berrange@redhat.com>
Message-ID: <20240103123005.2400437-1-berrange@redhat.com>
Reviewed-by: Zhao Liu <zhao1.liu@intel.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: 9f7ac8e8699dd7453a9140a8af5e57cf26d6459e
https://github.com/qemu/qemu/commit/9f7ac8e8699dd7453a9140a8af5e57cf26d6459e
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: 2024-01-11 (Thu, 11 Jan 2024)
Changed paths:
M tests/qtest/netdev-socket.c
Log Message:
-----------
Revert "netdev: set timeout depending on loadavg"
This reverts commit cadfc7293977ecadc2d6c48d7cffc553ed2f85f1.
The test was not timing out because of slow execution. It was
timing out due to a race condition leading to the client QEMU
attempting (and fatally failing) to connect before the server
QEMU was listening.
Signed-off-by: "Daniel P. Berrangé" <berrange@redhat.com>
Message-ID: <20240104162942.211458-2-berrange@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: 1a2253c71281c04acf1624401a2590fad1e2285b
https://github.com/qemu/qemu/commit/1a2253c71281c04acf1624401a2590fad1e2285b
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: 2024-01-11 (Thu, 11 Jan 2024)
Changed paths:
M include/qemu/osdep.h
M meson.build
Log Message:
-----------
Revert "osdep: add getloadavg"
This reverts commit dc864d3a3777424187280e50c9bfb84dced54f12.
This functionality is not required after the previous revert
Signed-off-by: "Daniel P. Berrangé" <berrange@redhat.com>
Message-ID: <20240104162942.211458-3-berrange@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: a298293866b277cb40ab24dcedda36c2b89ed2ab
https://github.com/qemu/qemu/commit/a298293866b277cb40ab24dcedda36c2b89ed2ab
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: 2024-01-11 (Thu, 11 Jan 2024)
Changed paths:
M tests/qtest/netdev-socket.c
Log Message:
-----------
Revert "tests/qtest/netdev-socket: Raise connection timeout to 120 seconds"
This reverts commit 0daaf2761f6d268ffaa2d01d450e202e127452b1.
The test was not timing out because of slow execution. It was
timing out due to a race condition leading to the client QEMU
attempting (and fatally failing) to connect before the server
QEMU was listening.
Signed-off-by: "Daniel P. Berrangé" <berrange@redhat.com>
Message-ID: <20240104162942.211458-4-berrange@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: cc91ca64d826acc0214ebf9428f5130b37deecd8
https://github.com/qemu/qemu/commit/cc91ca64d826acc0214ebf9428f5130b37deecd8
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: 2024-01-11 (Thu, 11 Jan 2024)
Changed paths:
M net/stream.c
M tests/qtest/netdev-socket.c
Log Message:
-----------
net: add explicit info about connecting/listening state
When running 'info network', if the stream backend is still in
the process of connecting, or waiting for an incoming connection,
no information is displayed.
There is also no way to distinguish whether the server is still
in the process of setting up the listener socket, or whether it
is ready to accept incoming client connections.
This leads to a race condition in the netdev-socket qtest which
launches a server process followed by a client process. Under
high load conditions it is possible for the client to attempt
to connect before the server is accepting clients. For the
scenarios which do not set the 'reconnect' option, this opens
up a race which can lead to the test scenario failing to reach
the expected state.
Now that 'info network' can distinguish between initialization
phase and the listening phase, the netdev-socket qtest will
correctly synchronize, such that the client QEMU is not spawned
until the server is ready.
This should solve the non-deterministic failures seen with the
netdev-socket qtest.
Signed-off-by: "Daniel P. Berrangé" <berrange@redhat.com>
Message-ID: <20240104162942.211458-5-berrange@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: 9cd67f0cce1887598b09b80cdeb066531102d743
https://github.com/qemu/qemu/commit/9cd67f0cce1887598b09b80cdeb066531102d743
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: 2024-01-11 (Thu, 11 Jan 2024)
Changed paths:
M net/stream.c
Log Message:
-----------
net: handle QIOTask completion to report useful error message
The network stream backend uses the async QIO socket APIs for listening
and connecting sockets. It does not check the task object completion
status, however, instead just looking at whether the socket FD is -1
or not.
By checking the task completion, we can set a useful error message for
users instead of the non-actionable "connection error" string.
eg so users will see:
(qemu) info network
net: index=0,type=stream,error: Failed to connect to '/foo.unix': No such file
or directory
Signed-off-by: "Daniel P. Berrangé" <berrange@redhat.com>
Message-ID: <20240104162942.211458-6-berrange@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: f51d3fb14d4125c00338e74eaa8bbe100f30e6f8
https://github.com/qemu/qemu/commit/f51d3fb14d4125c00338e74eaa8bbe100f30e6f8
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: 2024-01-11 (Thu, 11 Jan 2024)
Changed paths:
M tests/qtest/netdev-socket.c
Log Message:
-----------
qtest: ensure netdev-socket tests have non-overlapping names
When naming glib tests if the name of one test is a substring of the
name of another test, it is not possible to use the '-p /the/name'
option to run a single test.
Signed-off-by: "Daniel P. Berrangé" <berrange@redhat.com>
Message-ID: <20240104162942.211458-7-berrange@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: c98873ee4a0c2694aac976ab9affcf55da8b7e61
https://github.com/qemu/qemu/commit/c98873ee4a0c2694aac976ab9affcf55da8b7e61
Author: Samuel Tardieu <sam@rfc1149.net>
Date: 2024-01-11 (Thu, 11 Jan 2024)
Changed paths:
M tests/qtest/virtio-ccw-test.c
Log Message:
-----------
tests/qtest/virtio-ccw: Fix device presence checking
An apparent copy-paste error tests for the presence of the
virtio-rng-ccw device in order to perform tests on the virtio-scsi-ccw
device.
Signed-off-by: Samuel Tardieu <sam@rfc1149.net>
Message-ID: <20240106130121.1244993-1-sam@rfc1149.net>
Fixes: 65331bf5d1 ("tests/qtest: Check for virtio-ccw devices before using
them")
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: cdd30f369a21def5cfdd610753d319c29f75a0a8
https://github.com/qemu/qemu/commit/cdd30f369a21def5cfdd610753d319c29f75a0a8
Author: Nicholas Piggin <npiggin@gmail.com>
Date: 2024-01-11 (Thu, 11 Jan 2024)
Changed paths:
M .gitlab-ci.d/buildtest.yml
Log Message:
-----------
gitlab: fix s390x tag for avocado-system-centos
The 390x tag should be s390x.
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Message-ID: <20240107170119.82222-2-npiggin@gmail.com>
Reviewed-by: Cédric Le Goater <clg@kaod.org>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: 7af51621b16ae86646cc2dc9dee30de8176ff761
https://github.com/qemu/qemu/commit/7af51621b16ae86646cc2dc9dee30de8176ff761
Author: Thomas Huth <thuth@redhat.com>
Date: 2024-01-11 (Thu, 11 Jan 2024)
Changed paths:
M hw/s390x/ipl.c
M hw/s390x/ipl.h
M hw/s390x/s390-virtio-ccw.c
M target/s390x/kvm/pv.c
M target/s390x/kvm/pv.h
Log Message:
-----------
target/s390x/kvm/pv: Provide some more useful information if decryption fails
It's a common scenario to copy guest images from one host to another
to run the guest on the other machine. This (of course) does not work
with "secure execution" guests since they are encrypted with one certain
host key. However, if you still (accidentally) do it, you only get a
very user-unfriendly error message that looks like this:
qemu-system-s390x: KVM PV command 2 (KVM_PV_SET_SEC_PARMS) failed:
header rc 108 rrc 5 IOCTL rc: -22
Let's provide at least a somewhat nicer hint to the users so that they
are able to figure out what might have gone wrong.
Buglink: https://issues.redhat.com/browse/RHEL-18212
Message-ID: <20240110142916.850605-1-thuth@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: 469897ed4348341fda7b8db4ed1d1c1b753e59a4
https://github.com/qemu/qemu/commit/469897ed4348341fda7b8db4ed1d1c1b753e59a4
Author: Zhao Liu <zhao1.liu@intel.com>
Date: 2024-01-11 (Thu, 11 Jan 2024)
Changed paths:
M hw/s390x/s390-ccw.c
Log Message:
-----------
hw/s390x/ccw: Replace basename() with g_path_get_basename()
g_path_get_basename() is a portable utility function that has the
advantage of not modifying the string argument, so it should be
preferred over basename().
And also to avoid potential compile breakage with the Musl C library
similar to [1], replace basename() with g_path_get_basename().
[1]: https://lore.kernel.org/all/20231212010228.2701544-1-raj.khem@gmail.com/
Suggested-by: Cédric Le Goater <clg@redhat.com>
Signed-off-by: Zhao Liu <zhao1.liu@intel.com>
Message-ID: <20231221171921.57784-2-zhao1.liu@linux.intel.com>
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Reviewed-by: Eric Farman <farman@linux.ibm.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: 7af0cc147ce6394bed3ac7546c6c5ef82eac3bd6
https://github.com/qemu/qemu/commit/7af0cc147ce6394bed3ac7546c6c5ef82eac3bd6
Author: Zhao Liu <zhao1.liu@intel.com>
Date: 2024-01-11 (Thu, 11 Jan 2024)
Changed paths:
M hw/s390x/s390-ccw.c
Log Message:
-----------
hw/s390x/ccw: Replace dirname() with g_path_get_dirname()
As commit 3e015d815b3f ("use g_path_get_basename instead of basename")
said, g_path_get_dirname() should be preferred over dirname() since
the former is a portable utility function that has the advantage of not
modifying the string argument.
Replace dirname() with g_path_get_dirname().
Suggested-by: Cédric Le Goater <clg@redhat.com>
Signed-off-by: Zhao Liu <zhao1.liu@intel.com>
Message-ID: <20231221171921.57784-3-zhao1.liu@linux.intel.com>
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Reviewed-by: Eric Farman <farman@linux.ibm.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: e072af19fc06b18065f5081ff71cc7b2e6dca7bf
https://github.com/qemu/qemu/commit/e072af19fc06b18065f5081ff71cc7b2e6dca7bf
Author: Zhao Liu <zhao1.liu@intel.com>
Date: 2024-01-11 (Thu, 11 Jan 2024)
Changed paths:
M scripts/checkpatch.pl
Log Message:
-----------
scripts/checkpatch: Support codespell checking
Add two spelling check options (--codespell and --codespellfile) to
enhance spelling check through dictionary, which copied the Linux
kernel's implementation in checkpatch.pl.
This check uses the dictionary at "/usr/share/codespell/dictionary.txt"
by default, if there is no dictionary specified under this path, it
will look for the dictionary of python3's codespell (This requires user
to add python3's path in environment variable $PATH, and to install
codespell by "pip install codespell").
Tested-by: Yongwei Ma <yongwei.ma@intel.com>
Tested-by: Samuel Tardieu <sam@rfc1149.net>
Signed-off-by: Zhao Liu <zhao1.liu@intel.com>
Message-ID: <20240105083848.267192-1-zhao1.liu@linux.intel.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: e358a25a97c71c39e3513d9b869cdb82052e50b8
https://github.com/qemu/qemu/commit/e358a25a97c71c39e3513d9b869cdb82052e50b8
Author: Ilya Leoshkevich <iii@linux.ibm.com>
Date: 2024-01-11 (Thu, 11 Jan 2024)
Changed paths:
M target/s390x/tcg/translate.c
Log Message:
-----------
target/s390x: Fix LAE setting a wrong access register
LAE should set the access register corresponding to the first operand,
instead, it always modifies access register 1.
Co-developed-by: Ido Plat <Ido.Plat@ibm.com>
Cc: qemu-stable@nongnu.org
Fixes: a1c7610a6879 ("target-s390x: implement LAY and LAEY instructions")
Reviewed-by: David Hildenbrand <david@redhat.com>
Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
Message-ID: <20240111092328.929421-2-iii@linux.ibm.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: 2bcc91ecea99bd559fa551d80e6321027e01106d
https://github.com/qemu/qemu/commit/2bcc91ecea99bd559fa551d80e6321027e01106d
Author: Ilya Leoshkevich <iii@linux.ibm.com>
Date: 2024-01-11 (Thu, 11 Jan 2024)
Changed paths:
M tests/tcg/s390x/Makefile.target
A tests/tcg/s390x/lae.c
Log Message:
-----------
tests/tcg/s390x: Test LOAD ADDRESS EXTENDED
Add a small test to prevent regressions. Userspace runs in primary
mode, so LAE should always set the access register to 0.
Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
Message-ID: <20240111092328.929421-3-iii@linux.ibm.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: 52a21689cd829c1cc931b59b5ee5bdb10dd578c1
https://github.com/qemu/qemu/commit/52a21689cd829c1cc931b59b5ee5bdb10dd578c1
Author: Peter Maydell <peter.maydell@linaro.org>
Date: 2024-01-11 (Thu, 11 Jan 2024)
Changed paths:
M .gitlab-ci.d/buildtest.yml
Log Message:
-----------
.gitlab-ci.d/buildtest.yml: Work around htags bug when environment is large
Sometimes the CI "pages" job fails with a message like this from
htags:
$ htags -anT --tree-view=filetree -m qemu_init -t "Welcome to the QEMU
sourcecode"
htags: Negative exec line limit = -371
This is due to a bug in hflags where if the environment is too large it
falls over:
https://lists.gnu.org/archive/html/bug-global/2024-01/msg00000.html
This happens to us because GitLab CI puts the commit message of the
commit under test into the CI_COMMIT_MESSAGE and/or CI_COMMIT_TAG_MESSAGE
environment variables, so the job will fail if the commit happens to
have a verbose commit message.
Work around the htags bug by unsetting these variables while running
htags.
Cc: qemu-stable@nongnu.org
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2080
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Message-ID: <20240111125543.1573473-1-peter.maydell@linaro.org>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: b7f2aea63b1b4d3e20f48044f68cc0b0ee637ae3
https://github.com/qemu/qemu/commit/b7f2aea63b1b4d3e20f48044f68cc0b0ee637ae3
Author: Thomas Huth <thuth@redhat.com>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M tests/avocado/machine_microblaze.py
Log Message:
-----------
tests/avocado: Add a test for a little-endian microblaze machine
We've already got a test for a big endian microblaze machine, but so
far we lack one for a little endian machine. Now that the QEMU advent
calendar featured such an image, we can test the little endian mode,
too.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20231215161851.71508-1-thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Commit: b9371a7b907d2dfc7562729c9f2f5757354c5be4
https://github.com/qemu/qemu/commit/b9371a7b907d2dfc7562729c9f2f5757354c5be4
Author: Alex Bennée <alex.bennee@linaro.org>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M tests/avocado/kvm_xen_guest.py
Log Message:
-----------
tests/avocado: use snapshot=on in kvm_xen_guest
This ensures the rootfs is never permanently changed as we don't need
persistence between tests anyway.
Message-Id: <20240103173349.398526-3-alex.bennee@linaro.org>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Commit: 2d41bf0fe1f70021a22033901777cd4ab42ca68f
https://github.com/qemu/qemu/commit/2d41bf0fe1f70021a22033901777cd4ab42ca68f
Author: Alex Bennée <alex.bennee@linaro.org>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M .gitlab-ci.d/buildtest.yml
Log Message:
-----------
gitlab: include microblazeel in testing
This reverts aeb5f8f248e (gitlab: build the correct microblaze target)
now we actually have a little-endian test in avocado thanks to this
years advent calendar.
Message-Id: <20240103173349.398526-4-alex.bennee@linaro.org>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Commit: 67b5595d3b333fc5bcf82ce1e3aedc217b68b99a
https://github.com/qemu/qemu/commit/67b5595d3b333fc5bcf82ce1e3aedc217b68b99a
Author: Alex Bennée <alex.bennee@linaro.org>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M chardev/char-fe.c
M chardev/char.c
M include/chardev/char-fe.h
Log Message:
-----------
chardev: use bool for fe_is_open
The function qemu_chr_fe_init already treats be->fe_open as a bool and
if it acts like a bool it should be one. While we are at it make the
variable name more descriptive and add kdoc decorations.
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20231211145959.93759-1-alex.bennee@linaro.org>
Commit: 9eb95e5c56905365939017fc785312c59639e350
https://github.com/qemu/qemu/commit/9eb95e5c56905365939017fc785312c59639e350
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M tests/qtest/meson.build
Log Message:
-----------
qtest: bump min meson timeout to 60 seconds
Even some of the relatively fast qtests can sometimes hit the 30 second
timeout in GitLab CI under high parallelism/load conditions. Bump the
min to 60 seconds to give a higher margin for reliability.
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Message-ID: <20230717182859.707658-2-berrange@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20231215070357.10888-2-thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Commit: 70717951141451872cc0cba4d5d3a3cea5310525
https://github.com/qemu/qemu/commit/70717951141451872cc0cba4d5d3a3cea5310525
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M tests/qtest/meson.build
Log Message:
-----------
qtest: bump migration-test timeout to 8 minutes
The migration test should take between 1 min 30 and 2 mins on reasonably
modern hardware. The test is not especially compute bound, rather its
running time is dominated by the guest RAM size relative to the
bandwidth cap, which forces each iteration to take at least 30 seconds.
None the less under high load conditions with multiple QEMU processes
spawned and competing with other parallel tests, the worst case running
time might be somewhat extended. Bumping the timeout to 8 minutes gives
us good headroom, while still catching stuck tests relatively quickly.
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Message-ID: <20230717182859.707658-3-berrange@redhat.com>
[thuth: Bump timeout to 8 minutes to make it work on very loaded systems, too]
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20231215070357.10888-3-thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Commit: cb2218ab1637ed80f0f9abd41f60c43f24bb268a
https://github.com/qemu/qemu/commit/cb2218ab1637ed80f0f9abd41f60c43f24bb268a
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M tests/qtest/meson.build
Log Message:
-----------
qtest: bump qom-test timeout to 15 minutes
The qom-test is periodically hitting the 5 minute timeout when running
on the aarch64 emulator under GitLab CI. With an --enable-debug build
it can take over 10 minutes for arm/aarch64 targets. Setting timeout
to 15 minutes gives enough headroom to hopefully make it reliable.
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Message-ID: <20230717182859.707658-4-berrange@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20231215070357.10888-4-thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Commit: d05328bcb0f11a901e9f3e89ad01f2828a5ebe3a
https://github.com/qemu/qemu/commit/d05328bcb0f11a901e9f3e89ad01f2828a5ebe3a
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M tests/qtest/meson.build
Log Message:
-----------
qtest: bump npcm7xx_pwm-test timeout to 5 minutes
The npcm7xx_pwm-test takes 3 & 1/2 minutes in a --enable-debug build.
Bumping to 5 minutes will give more headroom.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-ID: <20230717182859.707658-5-berrange@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20231215070357.10888-5-thuth@redhat.com>
[AJB: s/pwn/pwm]
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Commit: f6d8d0e5429dbdad883530b7fa2bfdd0ace582ab
https://github.com/qemu/qemu/commit/f6d8d0e5429dbdad883530b7fa2bfdd0ace582ab
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M tests/qtest/meson.build
Log Message:
-----------
qtest: bump test-hmp timeout to 4 minutes
The hmp test takes just under 3 minutes in a --enable-debug
build. Bumping to 4 minutes will give more headroom.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-ID: <20230717182859.707658-6-berrange@redhat.com>
[thuth: fix copy-n-paste error in the description]
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20231215070357.10888-6-thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Commit: 17e164da121a939e7f09a01776b302c6554d1fc8
https://github.com/qemu/qemu/commit/17e164da121a939e7f09a01776b302c6554d1fc8
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M tests/qtest/meson.build
Log Message:
-----------
qtest: bump pxe-test timeout to 10 minutes
The pxe-test uses the boot_sector_test() function, and that already
uses a timeout of 600 seconds. So adjust the timeout on the meson
side accordingly.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
[thuth: Bump timeout to 600s and adjust commit description]
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20231215070357.10888-7-thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Commit: 8911563900db29ddc46b4660b7ee4771c8f1c9b6
https://github.com/qemu/qemu/commit/8911563900db29ddc46b4660b7ee4771c8f1c9b6
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M tests/qtest/meson.build
Log Message:
-----------
qtest: bump prom-env-test timeout to 6 minutes
The prom-env-test can take more than 5 minutes in a --enable-debug
build on a loaded system. Bumping to 6 minutes will give more headroom.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
[thuth: Bump timeout to 6 minutes instead of 3]
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20231215070357.10888-8-thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Commit: 93b6d67348df850eae074f8118d1e4f29622d8f7
https://github.com/qemu/qemu/commit/93b6d67348df850eae074f8118d1e4f29622d8f7
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M tests/qtest/meson.build
Log Message:
-----------
qtest: bump boot-serial-test timeout to 3 minutes
The boot-serial-test takes about 1 + 1/2 minutes in a --enable-debug
build. Bumping to 3 minutes will give more headroom.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-ID: <20230717182859.707658-9-berrange@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20231215070357.10888-9-thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Commit: f6bee9c2f21ae733eee6adace03228bf5d3fdc83
https://github.com/qemu/qemu/commit/f6bee9c2f21ae733eee6adace03228bf5d3fdc83
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M tests/qtest/meson.build
Log Message:
-----------
qtest: bump qos-test timeout to 2 minutes
The qos-test takes just under 1 minute in a --enable-debug
build. Bumping to 2 minutes will give more headroom.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-ID: <20230717182859.707658-10-berrange@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20231215070357.10888-10-thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Commit: e8a12fe31f776c60fec993513cd1b1e66c2b8e29
https://github.com/qemu/qemu/commit/e8a12fe31f776c60fec993513cd1b1e66c2b8e29
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M tests/qtest/meson.build
Log Message:
-----------
qtest: bump aspeed_smc-test timeout to 6 minutes
On a loaded system with --enable-debug, this test can take longer than
5 minutes. Raising the timeout to 6 minutes gives greater headroom for
such situations.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
[thuth: Increase the timeout to 6 minutes for very loaded systems]
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20231215070357.10888-11-thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Commit: 794876fb5281c93aeeac0ab007c938b755461d95
https://github.com/qemu/qemu/commit/794876fb5281c93aeeac0ab007c938b755461d95
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M tests/qtest/meson.build
Log Message:
-----------
qtest: bump bios-table-test timeout to 9 minutes
This is reliably hitting the current 2 minute timeout in GitLab CI,
and for the TCI job, it even hits a 6 minute timeout.
Reviewed-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Message-ID: <20230717182859.707658-12-berrange@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20231215070357.10888-12-thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Commit: 50dfa7ca4819f32aab5c915204b8eea684bca46e
https://github.com/qemu/qemu/commit/50dfa7ca4819f32aab5c915204b8eea684bca46e
Author: Thomas Huth <thuth@redhat.com>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M tests/qtest/meson.build
Log Message:
-----------
tests/qtest: Bump the device-introspect-test timeout to 12 minutes
When running the test in slow mode on a very loaded system with the
arm/aarch64 target and with --enable-debug, it can take longer than
10 minutes to finish the introspection test. Bump the timeout to twelve
minutes to make sure that it also finishes in such situations.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20231215070357.10888-13-thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Commit: c45f8f1aef35730a2dcf3cabe296ac12965db43d
https://github.com/qemu/qemu/commit/c45f8f1aef35730a2dcf3cabe296ac12965db43d
Author: Thomas Huth <thuth@redhat.com>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M tests/unit/meson.build
Log Message:
-----------
tests/unit: Bump test-aio-multithread test timeout to 2 minutes
When running the tests in slow mode on a very loaded system and with
--enable-debug, the test-aio-multithread can take longer than 1 minute.
Bump the timeout to two minutes to make sure that it also passes in
such situations.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20231215070357.10888-14-thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Commit: e1b363e328d559cd5f86d3d1d7b84d0154e153d3
https://github.com/qemu/qemu/commit/e1b363e328d559cd5f86d3d1d7b84d0154e153d3
Author: Thomas Huth <thuth@redhat.com>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M tests/unit/meson.build
Log Message:
-----------
tests/unit: Bump test-crypto-block test timeout to 5 minutes
When running the tests in slow mode on a very loaded system and with
--enable-debug, the test-crypto-block can take longer than 4 minutes.
Bump the timeout to 5 minutes to make sure that it also passes in
such situations.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20231215070357.10888-15-thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Commit: 92b1dba3b0708fb054b96bd022b84857b8b047a9
https://github.com/qemu/qemu/commit/92b1dba3b0708fb054b96bd022b84857b8b047a9
Author: Thomas Huth <thuth@redhat.com>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M tests/fp/meson.build
Log Message:
-----------
tests/fp: Bump fp-test-mulAdd test timeout to 3 minutes
When running the tests in slow mode with --enable-debug on a very loaded
system, the fp-test-mulAdd test can take longer than 2 minutes. Bump the
timeout to three minutes to make sure it passes in such situations, too.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20231215070357.10888-16-thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Commit: 4156325cd3c205ce77b82de2c48127ccacddaf5b
https://github.com/qemu/qemu/commit/4156325cd3c205ce77b82de2c48127ccacddaf5b
Author: Daniel P. Berrangé <berrange@redhat.com>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M scripts/mtest2make.py
Log Message:
-----------
mtest2make: stop disabling meson test timeouts
The mtest2make.py script passes the arg '-t 0' to 'meson test' which
disables all test timeouts. This is a major source of pain when running
in GitLab CI and a test gets stuck. It will stall until GitLab kills the
CI job. This leaves us with little easily consumable information about
the stalled test. The TAP format doesn't show the test name until it is
completed, and TAP output from multiple tests it interleaved. So we
have to analyse the log to figure out what tests had un-finished TAP
output present and thus infer which test case caused the hang. This is
very time consuming and error prone.
By allowing meson to kill stalled tests, we get a direct display of what
test program got stuck, which lets us more directly focus in on what
specific test case within the test program hung.
The other issue with disabling meson test timeouts by default is that it
makes it more likely that maintainers inadvertantly introduce slowdowns.
For example the recent-ish change that accidentally made migrate-test
take 15-20 minutes instead of around 1 minute.
The main risk of this change is that the individual test timeouts might
be too short to allow completion in high load scenarios. Thus, there is
likely to be some short term pain where we have to bump the timeouts for
certain tests to make them reliable enough. The preceeding few patches
raised the timeouts for all failures that were immediately apparent
in GitLab CI.
Even with the possible short term instability, this should still be a
net win for debuggability of failed CI pipelines over the long term.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Message-ID: <20230717182859.707658-13-berrange@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20231215070357.10888-17-thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Commit: b16a45bc5e0e329a16af8a2e020a6e7044f9afa2
https://github.com/qemu/qemu/commit/b16a45bc5e0e329a16af8a2e020a6e7044f9afa2
Author: Alex Bennée <alex.bennee@linaro.org>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M .readthedocs.yml
A docs/requirements.txt
Log Message:
-----------
readthodocs: fully specify a build environment
This is now expected by rtd so I've expanded using their example as
22.04 is one of our supported platforms. I tried to work out if there
was an easy way to re-generate a requirements.txt from our
pythondeps.toml but in the end went for the easier solution.
Cc: <qemu-stable@nongnu.org>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20231221174200.2693694-1-alex.bennee@linaro.org>
Commit: 139db3cc5967e995e039c9cc2228c627cef7c1cf
https://github.com/qemu/qemu/commit/139db3cc5967e995e039c9cc2228c627cef7c1cf
Author: Alex Bennée <alex.bennee@linaro.org>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M tests/avocado/replay_kernel.py
Log Message:
-----------
tests/avocado: partially revert unmasking of replay_linux tests
It seems we were premature in declaring replay_linux.py fixed. The
x86_64 image still seems to hang occasionally. I've raised a new bug
to cover it:
https://gitlab.com/qemu-project/qemu/-/issues/2094
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Commit: 393d5c5bc717b18cd361b4a1ffbfe2a18b29a03b
https://github.com/qemu/qemu/commit/393d5c5bc717b18cd361b4a1ffbfe2a18b29a03b
Author: Gavin Shan <gshan@redhat.com>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M hw/core/machine.c
Log Message:
-----------
numa: Skip invalidation of cluster and NUMA node boundary for qtest
There are warning messages printed from tests/qtest/numa-test.c,
to complain the CPU cluster and NUMA node boundary is broken. Since
the broken boundary is expected, we don't want to see the warning
messages.
# cd /home/gavin/sandbox/qemu.main/build
# MALLOC_PERTURB_=255 QTEST_QEMU_BINARY=./qemu-system-aarch64 \
G_TEST_DBUS_DAEMON=../tests/dbus-vmstate-daemon.sh \
QTEST_QEMU_IMG=./qemu-img \
QTEST_QEMU_STORAGE_DAEMON_BINARY=./storage-daemon/qemu-storage-daemon \
tests/qtest/numa-test --tap -k
:
qemu-system-aarch64: warning: CPU-0 and CPU-4 in socket-0-cluster-0 \
have been associated with node-0 and node-1 respectively. \
It can cause OSes like Linux to misbehave
:
Skip the invalidation of CPU cluster and NUMA node boundary when
qtest is enabled, to avoid the warning messages.
Fixes: a494fdb715 ("numa: Validate cluster and NUMA node boundary if required")
Signed-off-by: Gavin Shan <gshan@redhat.com>
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Commit: b1b1585558785281e06d30157b0bc27549fd5c55
https://github.com/qemu/qemu/commit/b1b1585558785281e06d30157b0bc27549fd5c55
Author: Peter Maydell <peter.maydell@linaro.org>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M .gitlab-ci.d/buildtest.yml
M hw/m68k/q800.c
M hw/s390x/ipl.c
M hw/s390x/ipl.h
M hw/s390x/s390-ccw.c
M hw/s390x/s390-virtio-ccw.c
M include/hw/m68k/q800.h
M include/qemu/osdep.h
M meson.build
M net/stream.c
M scripts/checkpatch.pl
M target/s390x/kvm/pv.c
M target/s390x/kvm/pv.h
M target/s390x/tcg/translate.c
M tests/qtest/netdev-socket.c
M tests/qtest/virtio-ccw-test.c
M tests/qtest/virtio-net-failover.c
M tests/tcg/s390x/Makefile.target
A tests/tcg/s390x/lae.c
Log Message:
-----------
Merge tag 'pull-request-2024-01-11' of https://gitlab.com/thuth/qemu into
staging
* Fix non-deterministic failures of the 'netdev-socket' qtest
* Fix device presence checking in the virtio-ccw qtest
* Support codespell checking in checkpatch.pl
* Fix emulation of LAE s390x instruction
* Work around htags bug when environment is large
* Some other small clean-ups here and there
# -----BEGIN PGP SIGNATURE-----
#
# iQJFBAABCAAvFiEEJ7iIR+7gJQEY8+q5LtnXdP5wLbUFAmWgHlgRHHRodXRoQHJl
# ZGhhdC5jb20ACgkQLtnXdP5wLbXAnBAAjQve/Jmfp9p8eQmswG7cl/a2TuJ59b9X
# SFRja2PprV/Wp4kxxEJX4er9F2+rlMusNL62LBp/QjZi9u4lCvCmuB7sMa0wEkjr
# BPPBrkxkAT+/8vhGpYg2GrxZv/UOLkycp3sjEp4v5yXWQw+OEBnkZZ+AuHddpnEr
# NKMKss71uQmccvuzD5FMDfbJQcSBD/yGPyFfDrv1RKreYRlbkEDVlcVoZpfoMwQY
# Pl167iDdmjVtsT+4wf8vHo5W/AYKDOjlV6AoujCnJVZnGx6BtDLiF/iNJ/VU1Ty5
# cRxySPT64HG+cGrbRqz9IjDvs++WW5EQn1jPY8NO2XFz3sney6Cs/pLKjqJY9S7P
# kfOXOBZG3zOI1kgd/CSR5b4szg4XvtTZaupczKiGOpYC9klf0oQNXGU5jXi3Csop
# Q332oUgiPeNdOx/4tXobFX6RwVCqLRYZbHx9RRYSxWlqJJPAB74/n+RZsmOtsxuJ
# RaiPKDmbVlslkUm78gIa5e6DMwDk2wmlkqa64W7VZxyqfQTRDPiPvfMGePkj6tmZ
# h9vUsELwwORlHpZyL08n0fzs3aeIYwzPwhfr+5iQZIawIp4Zqo8i8Lic/WfIlok9
# rmPIA0mjs1VtrUsroItw4NcY04xcVa7hkhz4EbkZROrfGamdkLuvbk2OKuOeoL0U
# lpgtQL6jA7E=
# =F/j2
# -----END PGP SIGNATURE-----
# gpg: Signature made Thu 11 Jan 2024 16:59:04 GMT
# gpg: using RSA key 27B88847EEE0250118F3EAB92ED9D774FE702DB5
# gpg: issuer "thuth@redhat.com"
# gpg: Good signature from "Thomas Huth <th.huth@gmx.de>" [full]
# gpg: aka "Thomas Huth <thuth@redhat.com>" [full]
# gpg: aka "Thomas Huth <huth@tuxfamily.org>" [full]
# gpg: aka "Thomas Huth <th.huth@posteo.de>" [unknown]
# Primary key fingerprint: 27B8 8847 EEE0 2501 18F3 EAB9 2ED9 D774 FE70 2DB5
* tag 'pull-request-2024-01-11' of https://gitlab.com/thuth/qemu:
.gitlab-ci.d/buildtest.yml: Work around htags bug when environment is large
tests/tcg/s390x: Test LOAD ADDRESS EXTENDED
target/s390x: Fix LAE setting a wrong access register
scripts/checkpatch: Support codespell checking
hw/s390x/ccw: Replace dirname() with g_path_get_dirname()
hw/s390x/ccw: Replace basename() with g_path_get_basename()
target/s390x/kvm/pv: Provide some more useful information if decryption fails
gitlab: fix s390x tag for avocado-system-centos
tests/qtest/virtio-ccw: Fix device presence checking
qtest: ensure netdev-socket tests have non-overlapping names
net: handle QIOTask completion to report useful error message
net: add explicit info about connecting/listening state
Revert "tests/qtest/netdev-socket: Raise connection timeout to 120 seconds"
Revert "osdep: add getloadavg"
Revert "netdev: set timeout depending on loadavg"
qtest: use correct boolean type for failover property
q800: move dp8393x_prom memory region to Q800MachineState
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Commit: 977542ded7e6b28d2bc077bcda24568c716e393c
https://github.com/qemu/qemu/commit/977542ded7e6b28d2bc077bcda24568c716e393c
Author: Peter Maydell <peter.maydell@linaro.org>
Date: 2024-01-12 (Fri, 12 Jan 2024)
Changed paths:
M .gitlab-ci.d/buildtest.yml
M .readthedocs.yml
M chardev/char-fe.c
M chardev/char.c
A docs/requirements.txt
M include/chardev/char-fe.h
M scripts/mtest2make.py
M tests/avocado/kvm_xen_guest.py
M tests/avocado/machine_microblaze.py
M tests/avocado/replay_kernel.py
M tests/fp/meson.build
M tests/qtest/meson.build
M tests/unit/meson.build
Log Message:
-----------
Merge tag 'pull-testing-updates-120124-2' of https://gitlab.com/stsquad/qemu
into staging
testing and misc updates
- add LE microblaze test to avocado
- use modern snapshot=on to avoid trashing disk image
- use plain bool for fe_is_open
- various updates to qtest timeouts
- enable meson test timeouts
- tweak the readthedocs environment
- partially revert un-flaking x86_64
# -----BEGIN PGP SIGNATURE-----
#
# iQEzBAABCgAdFiEEZoWumedRZ7yvyN81+9DbCVqeKkQFAmWhPccACgkQ+9DbCVqe
# KkS5agf+OoW6HOitt34YeL6cGGtIKaxbta+Fs6jq+ucIbN63TmLTuKrmPiRNxjuo
# Fj2Qvh9R7Tl7Q/a7ZAym0Fze7GtsvvsidkiQS4pmi9vYuJrhS734CxXHT8JS6zJr
# ymQ0nGZODg1cVB4oAR9sXo/OwEQdDTSgKp8wdNr930fxYwokUKBUgcOqElu3SWHv
# duSYDuaflnP5B8ZGbb1ZnOlwS9lZIHTwjZyN5J1YtxF0T8Ez4A+xseEOpQ/00MoE
# Ecjdp3ELCxzOI+1U33Yni7ol//fxQpRKi+xf2fGIxhuSA3i32rmY5NWTvl7VwuS1
# gXryjX2rukSujySP3vkdtTp0dmkbpg==
# =ZuDd
# -----END PGP SIGNATURE-----
# gpg: Signature made Fri 12 Jan 2024 13:25:27 GMT
# gpg: using RSA key 6685AE99E75167BCAFC8DF35FBD0DB095A9E2A44
# gpg: Good signature from "Alex Bennée (Master Work Key)
<alex.bennee@linaro.org>" [full]
# Primary key fingerprint: 6685 AE99 E751 67BC AFC8 DF35 FBD0 DB09 5A9E 2A44
* tag 'pull-testing-updates-120124-2' of https://gitlab.com/stsquad/qemu: (22
commits)
tests/avocado: partially revert unmasking of replay_linux tests
readthodocs: fully specify a build environment
mtest2make: stop disabling meson test timeouts
tests/fp: Bump fp-test-mulAdd test timeout to 3 minutes
tests/unit: Bump test-crypto-block test timeout to 5 minutes
tests/unit: Bump test-aio-multithread test timeout to 2 minutes
tests/qtest: Bump the device-introspect-test timeout to 12 minutes
qtest: bump bios-table-test timeout to 9 minutes
qtest: bump aspeed_smc-test timeout to 6 minutes
qtest: bump qos-test timeout to 2 minutes
qtest: bump boot-serial-test timeout to 3 minutes
qtest: bump prom-env-test timeout to 6 minutes
qtest: bump pxe-test timeout to 10 minutes
qtest: bump test-hmp timeout to 4 minutes
qtest: bump npcm7xx_pwm-test timeout to 5 minutes
qtest: bump qom-test timeout to 15 minutes
qtest: bump migration-test timeout to 8 minutes
qtest: bump min meson timeout to 60 seconds
chardev: use bool for fe_is_open
gitlab: include microblazeel in testing
...
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Compare: https://github.com/qemu/qemu/compare/3fab43d2f638...977542ded7e6