Branch: refs/heads/staging
Home: https://github.com/qemu/qemu
Commit: 2abdc8cad0b97f5a98a0e4329a07a658c630ce54
https://github.com/qemu/qemu/commit/2abdc8cad0b97f5a98a0e4329a07a658c630ce54
Author: Daniel P. Berrangé <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M tests/functional/test_mips64el_malta.py
Log Message:
-----------
tests/functional: fix mips64el test to honour workdir
The missing directory separator resulted in the kernel file being
created 1 level higher than expected.
Reviewed-by: Alex Bennée <[email protected]>
Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
Signed-off-by: Daniel P. Berrangé <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: dbaaef7dbfe3a932279c2d77f056a30575cc97cb
https://github.com/qemu/qemu/commit/dbaaef7dbfe3a932279c2d77f056a30575cc97cb
Author: Daniel P. Berrangé <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M docs/devel/testing/functional.rst
M tests/functional/qemu_test/testcase.py
Log Message:
-----------
tests/functional: automatically clean up scratch files after tests
The build/tests/functional subdirectories are consuming huge amounts
of disk space.
Split the location for scratch files into a 'scratch' sub-directory,
separate from log files, and delete it upon completion of each test.
The new env variable QEMU_TEST_KEEP_SCRATCH can be set to preserve
this scratch dir for debugging access if required.
Reviewed-by: Alex Bennée <[email protected]>
Signed-off-by: Daniel P. Berrangé <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: b0b5bc2dc6580d87ead7ff7a5ba51c8a2358bf52
https://github.com/qemu/qemu/commit/b0b5bc2dc6580d87ead7ff7a5ba51c8a2358bf52
Author: Daniel P. Berrangé <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M tests/functional/test_mips64el_malta.py
Log Message:
-----------
tests/functional: remove "AVOCADO" from env variable name
This env variable is a debugging flag to save screendumps in the
mips64el malta tests.
Reviewed-by: Alex Bennée <[email protected]>
Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
Signed-off-by: Daniel P. Berrangé <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: 200cd4b081732c27e50262287ff3f07bf0211f08
https://github.com/qemu/qemu/commit/200cd4b081732c27e50262287ff3f07bf0211f08
Author: Daniel P. Berrangé <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M tests/functional/test_m68k_nextcube.py
Log Message:
-----------
tests/functional: remove todo wrt avocado.utils.wait_for
We're not using avocado anymore, so while the TODO item is still
relevant, suggesting use of avocado.utils is not.
Reviewed-by: Alex Bennée <[email protected]>
Signed-off-by: Daniel P. Berrangé <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: b12b4dbcd0ce9fe5c87c4ebdf1f11eb614ff515a
https://github.com/qemu/qemu/commit/b12b4dbcd0ce9fe5c87c4ebdf1f11eb614ff515a
Author: Daniel P. Berrangé <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M tests/functional/test_arm_bpim2u.py
M tests/functional/test_arm_orangepi.py
Log Message:
-----------
tests/functional: remove leftover :avocado: tags
These tags are not honoured under the new functional test harness.
Reviewed-by: Alex Bennée <[email protected]>
Signed-off-by: Daniel P. Berrangé <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: 57e504ad4f0cc2037aebf18b1ca6f73c8a4b304b
https://github.com/qemu/qemu/commit/57e504ad4f0cc2037aebf18b1ca6f73c8a4b304b
Author: Daniel P. Berrangé <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M tests/functional/qemu_test/tuxruntest.py
Log Message:
-----------
tests/functional: remove obsolete reference to avocado bug
Historical bugs in avocado related to zstd support are not relevant to
the code now that it uses QEMU's native test harness.
Reviewed-by: Alex Bennée <[email protected]>
Signed-off-by: Daniel P. Berrangé <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: ebc88b2d54cb4cb29149816a9d1942d548b1ebd9
https://github.com/qemu/qemu/commit/ebc88b2d54cb4cb29149816a9d1942d548b1ebd9
Author: Daniel P. Berrangé <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M tests/functional/test_acpi_bits.py
Log Message:
-----------
tests/functional: remove comments talking about avocado
The first comment is still relevant but should talk about our own test
harness instead. The second comment adds no value over reading the code
and can be removed.
Signed-off-by: Daniel P. Berrangé <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Pierrick Bouvier <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: 03d6c237ccd98f2873d1dc59287f163ad0eb83ee
https://github.com/qemu/qemu/commit/03d6c237ccd98f2873d1dc59287f163ad0eb83ee
Author: Daniel P. Berrangé <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M tests/functional/test_acpi_bits.py
Log Message:
-----------
tests/functional: honour self.workdir in ACPI bits tests
The ACPI bits test sets up its own private temporary directory into it
creates scratch files. This is justified by a suggestion that we need
to be able to preserve the scratch files. We have the ability to
preserve the scratch dir with our functional harness, so there's no
reason to diverge from standard practice in file placement.
Reviewed-by: Alex Bennée <[email protected]>
Signed-off-by: Daniel P. Berrangé <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: e6d69e0f3b83b7c60d024f41f5eaf130755b090c
https://github.com/qemu/qemu/commit/e6d69e0f3b83b7c60d024f41f5eaf130755b090c
Author: Daniel P. Berrangé <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M tests/functional/qemu_test/testcase.py
Log Message:
-----------
tests/functional: put QEMUMachine logs in testcase log directory
We are not passing the 'log_dir' parameter to QEMUMachine, so the
QEMU stdout/err logs are being placed in a temp directory and thus
deleted after execution. This makes them inaccessible as gitlab
CI artifacts.
Pass the testcase log directory path into QEMUMachine to make the
logs persistent.
Reviewed-by: Alex Bennée <[email protected]>
Signed-off-by: Daniel P. Berrangé <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: 9f85aff93f5dcedb70819a5ed7796b6df90fdf2d
https://github.com/qemu/qemu/commit/9f85aff93f5dcedb70819a5ed7796b6df90fdf2d
Author: Daniel P. Berrangé <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M tests/functional/qemu_test/testcase.py
Log Message:
-----------
tests/functional: honour requested test VM name in QEMUMachine
The functional test case class is going to the trouble of passing
around a machine name, but then fails to give this QEMUMachine. As
a result, QEMUMachine will create a completely random name. Since
log file names match the machine name, this results in log files
accumulating over time.
Reviewed-by: Thomas Huth <[email protected]>
Signed-off-by: Daniel P. Berrangé <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: 9bcfead1ee1c5d37c39b129557e1528879270fea
https://github.com/qemu/qemu/commit/9bcfead1ee1c5d37c39b129557e1528879270fea
Author: Daniel P. Berrangé <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M tests/functional/qemu_test/testcase.py
Log Message:
-----------
tests/functional: enable debug logging for QEMUMachine
Set the 'qemu.machine' logger to 'DEBUG' level, to ensure we see log
messages related to the QEMUMachine class. Most importantly this
ensures we capture the full QEMU command line args for instances we
spawn.
Signed-off-by: Daniel P. Berrangé <[email protected]>
Message-Id: <[email protected]>
Tested-by: Thomas Huth <[email protected]>
Reviewed-by: Thomas Huth <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Reviewed-by: Thomas Huth <[email protected]>
Message-Id: <[email protected]>
Commit: 6f0942b723df9441fe3304e8ab6d87bb17f88a1e
https://github.com/qemu/qemu/commit/6f0942b723df9441fe3304e8ab6d87bb17f88a1e
Author: Daniel P. Berrangé <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M tests/functional/qemu_test/cmd.py
Log Message:
-----------
tests/functional: logs details of console interaction operations
When functional tests go wrong, it will often be related to the console
interaction wait state. By logging the messages that we're looking for,
and data we're about to be sending, it'll be easier to diagnose where
tests are getting stuck.
Signed-off-by: Daniel P. Berrangé <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Thomas Huth <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: 7699e37b2ac32ba4b905b4b22024e93f33337ce7
https://github.com/qemu/qemu/commit/7699e37b2ac32ba4b905b4b22024e93f33337ce7
Author: Daniel P. Berrangé <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M tests/functional/test_virtio_gpu.py
Log Message:
-----------
tests/functional: don't try to wait for the empty string
Telling exec_command_wand_wait_for_pattern to wait for the empty
string does not make any conceptual sense, as a check for empty
string will always succeed. It makes even less sense when followed
by a call to wait_for_console_pattern() with a real match.
Signed-off-by: Daniel P. Berrangé <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Thomas Huth <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: f03a81897db14bb56109b6adc8699a91774b3389
https://github.com/qemu/qemu/commit/f03a81897db14bb56109b6adc8699a91774b3389
Author: Daniel P. Berrangé <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M tests/functional/qemu_test/cmd.py
Log Message:
-----------
tests/functional: require non-NULL success_message for console wait
When waiting for expected output, the 'success_message' is a mandatory
parameter, with 'failure_message' defaulting to None.
The code has logic which indicates it was trying to cope with
'success_message' being None and 'failure_message' being non-None but
it does not appear able to actually do anything useful. The check for
'success_message is None' will break out of the loop before any check
for 'failure_message' has been performed.
IOW, for practcal purposes 'success_message' must be non-None unless
'send_string' is set. Assert this expectation and simplify the loop
logic.
Signed-off-by: Daniel P. Berrangé <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Thomas Huth <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: cdad03b74f759857d784e074755f0d96a64d69af
https://github.com/qemu/qemu/commit/cdad03b74f759857d784e074755f0d96a64d69af
Author: Daniel P. Berrangé <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M tests/functional/qemu_test/cmd.py
Log Message:
-----------
tests/functional: rewrite console handling to be bytewise
The console interaction that waits for predicted strings uses
readline(), and thus is only capable of waiting for strings
that are followed by a newline.
This is inconvenient when needing to match on some things,
particularly login prompts, or shell prompts, causing tests
to use time.sleep(...) instead, which is unreliable.
Switch to reading the console 1 byte at a time, comparing
against the success/failure messages until we see a match,
regardless of whether a newline is encountered.
The success/failure comparisons are done with the python bytes
type, rather than strings, to avoid the problem of needing to
decode partially received multibyte utf8 characters.
Heavily inspired by a patch proposed by Cédric, but written
again to work in bytes, rather than strings.
Co-developed-by: Cédric Le Goater <[email protected]>
Signed-off-by: Daniel P. Berrangé <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: 97d79319f0475fe248962166d9ec4ecf6477d8cc
https://github.com/qemu/qemu/commit/97d79319f0475fe248962166d9ec4ecf6477d8cc
Author: Daniel P. Berrangé <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M tests/functional/qemu_test/tuxruntest.py
Log Message:
-----------
tests/functional: remove time.sleep usage from tuxrun tests
The tuxrun tests send a series of strings to the guest to login
and then run commands. Since we have been unable to match on
console output that isn't followed by a newline, the test used
many time.sleep() statements to pretend to synchronize with
the guest.
This has proved to be unreliable for the aarch64be instance of
the tuxrun tests, with the test often hanging. The hang is a
very subtle timing problem, and it is suspected that some
(otherwise apparently harmless) I/O error messages could be
resulting in full FIFO buffers, stalling interaction with
the guest.
With the newly rewritten console interaction able to match
strings that don't have a following newline, the tux run
tests can now match directly on the login prompt, and/or
shell PS1 prompt.
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2689
Signed-off-by: Daniel P. Berrangé <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Thomas Huth <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: 1a8755a51eef11360af92adf71fed6a20a1260b2
https://github.com/qemu/qemu/commit/1a8755a51eef11360af92adf71fed6a20a1260b2
Author: Daniel P. Berrangé <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M docs/devel/testing/functional.rst
M tests/functional/qemu_test/testcase.py
Log Message:
-----------
tests/functional: add a QMP backdoor for debugging stalled tests
Support the QEMU_TEST_QMP_BACKDOOR=backdoor.sock env variable as a
way to get a QMP backdoor for debugging a stalled QEMU test. Most
typically this would be used if running the tests directly:
$ QEMU_TEST_QMP_BACKDOOR=backdoor.sock \
QEMU_TEST_QEMU_BINARY=./build/qemu-system-arm \
PYTHONPATH=./python \
./tests/functional/test_arm_tuxrun.py
And then, when the test stalls, in a second shell run:
$ ./scripts/qmp/qmp-shell backdoor.sock
Signed-off-by: Daniel P. Berrangé <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Thomas Huth <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: f5578e427f95cb34436a18c0cd4417d4280e61bc
https://github.com/qemu/qemu/commit/f5578e427f95cb34436a18c0cd4417d4280e61bc
Author: Daniel P. Berrangé <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M tests/functional/qemu_test/testcase.py
Log Message:
-----------
tests/functional: avoid accessing log_filename on earlier failures
If a failure occurs early in the QemuBaseTest constructor, the
'log_filename' object atttribute may not exist yet. This happens
most notably if the QEMU_TEST_QEMU_BINARY is not set. We can't
initialize 'log_filename' earlier as we use the binary to identify
the architecture which is then used to build the path in which the
logs are stored.
Signed-off-by: Daniel P. Berrangé <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Thomas Huth <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: 3713690264ea752e84df1369efa0584e5e46bfe2
https://github.com/qemu/qemu/commit/3713690264ea752e84df1369efa0584e5e46bfe2
Author: Thomas Huth <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M MAINTAINERS
R tests/avocado/tuxrun_baselines.py
M tests/functional/meson.build
A tests/functional/test_aarch64_tuxrun.py
Log Message:
-----------
tests/functional: Convert the Avocado aarch64 tuxrun tests
Move the tests to a new file so that they can be run via
qemu-system-aarch64 in the functional framework.
Since these were the last tests in tests/avocado/tuxrun_baselines.py,
we can now remove that file, too.
Signed-off-by: Thomas Huth <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: abf7c0f1adb3f2fd6f429d449cb68d266db85069
https://github.com/qemu/qemu/commit/abf7c0f1adb3f2fd6f429d449cb68d266db85069
Author: Alex Bennée <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M tests/functional/test_aarch64_tuxrun.py
Log Message:
-----------
tests/functional: update the aarch64 tuxrun tests
Now there are new up to date images available we should update to them.
With the new rootfs the blk I/O errors also go away on arm64be.
Cc: Anders Roxell <[email protected]>
Reviewed-by: Thomas Huth <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: cfa3a6c54511374e9ccee26d9c38ac1698fc7af2
https://github.com/qemu/qemu/commit/cfa3a6c54511374e9ccee26d9c38ac1698fc7af2
Author: Pierrick Bouvier <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M include/qemu/qemu-plugin.h
Log Message:
-----------
plugins: add missing export for qemu_plugin_num_vcpus
Fixes: 4a448b148ca ("plugins: add qemu_plugin_num_vcpus function")
Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
Signed-off-by: Pierrick Bouvier <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Richard Henderson <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: 1ef08e341f2e134bb06f1a5279032fc44917183b
https://github.com/qemu/qemu/commit/1ef08e341f2e134bb06f1a5279032fc44917183b
Author: Pierrick Bouvier <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M MAINTAINERS
M plugins/meson.build
A scripts/qemu-plugin-symbols.py
Log Message:
-----------
plugins: detect qemu plugin API symbols from header
Instead of using a static file (error prone and hard to keep in sync),
we generate it using a script.
Note: if a symbol is not exported, we'll now notice it when linking for
Windows/MacOS platforms.
Signed-off-by: Pierrick Bouvier <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: 8ac1719df75cba01e7095e990265b957aed4f1c2
https://github.com/qemu/qemu/commit/8ac1719df75cba01e7095e990265b957aed4f1c2
Author: Pierrick Bouvier <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
R plugins/qemu-plugins.symbols
Log Message:
-----------
plugins: eradicate qemu-plugins.symbols static file
Signed-off-by: Pierrick Bouvier <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: f7ceab1e307128c2e07bee1f92fd57d4a948b1f8
https://github.com/qemu/qemu/commit/f7ceab1e307128c2e07bee1f92fd57d4a948b1f8
Author: Junjie Mao <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M rust/hw/char/pl011/src/device.rs
Log Message:
-----------
rust/pl011: Fix range checks for device ID accesses
The peripheral and PrimeCell identification registers of pl011 are located at
offset 0xFE0 - 0xFFC. To check if a read falls to such registers, the C
implementation checks if the offset-shifted-by-2 (not the offset itself) is in
the range 0x3F8 - 0x3FF.
Use the same check in the Rust implementation.
This fixes the timeout of the following avocado tests:
* tests/avocado/boot_linux_console.py:BootLinuxConsole.test_arm_virt
* tests/avocado/replay_kernel.py:ReplayKernelNormal.test_arm_virt
* tests/avocado/replay_kernel.py:ReplayKernelNormal.test_arm_vexpressa9
Reported-by: Peter Maydell <[email protected]>
Signed-off-by: Junjie Mao <[email protected]>
Tested-by: Alex Bennée <[email protected]>
Reviewed-by: Alex Bennée <[email protected]>
Message-Id:
<sy0p300mb102644c4ac34a3aad75dc4d595...@sy0p300mb1026.ausp300.prod.outlook.com>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: 270c81b7d599882118794aaf2196a4e829937fbe
https://github.com/qemu/qemu/commit/270c81b7d599882118794aaf2196a4e829937fbe
Author: Daniel P. Berrangé <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M .gitlab-ci.d/check-dco.py
M docs/devel/submitting-a-patch.rst
Log Message:
-----------
docs: explicitly permit a "commonly known identity" with SoB
The docs for submitting a patch describe using your "Real Name" with
the Signed-off-by line. Although somewhat ambiguous, this has often
been interpreted to mean someone's legal name.
In recent times, there's been a general push back[1] against the notion
that use of Signed-off-by in a project automatically requires / implies
the use of legal ("real") names and greater awareness of the downsides.
Full discussion of the problems of such policies is beyond the scope of
this commit message, but at a high level they are liable to marginalize,
disadvantage, and potentially result in harm, to contributors.
TL;DR: there are compelling reasons for a person to choose distinct
identities in different contexts & a decision to override that choice
should not be taken lightly.
A number of key projects have responded to the issues raised by making
it clear that a contributor is free to determine the identity used in
SoB lines:
* Linux has clarified[2] that they merely expect use of the
contributor's "known identity", removing the previous explicit
rejection of pseudonyms.
* CNCF has clarified[3] that the real name is simply the identity
the contributor chooses to use in the context of the community
and does not have to be a legal name, nor birth name, nor appear
on any government ID.
Since we have no intention of ever routinely checking any form of ID
documents for contributors[4], realistically we have no way of knowing
anything about the name they are using, except through chance, or
through the contributor volunteering the information. IOW, we almost
certainly already have people using pseudonyms for contributions.
This proposes to accept that reality and eliminate unnecessary friction,
by following Linux & the CNCF in merely asking that a contributors'
commonly known identity, of their choosing, be used with the SoB line.
[1] Raised in many contexts at many times, but a decent overall summary
can be read at https://drewdevault.com/2023/10/31/On-real-names.html
[2]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d4563201f33a022fc0353033d9dfeb1606a88330
[3] https://github.com/cncf/foundation/blob/659fd32c86dc/dco-guidelines.md
[4] Excluding the rare GPG key signing parties for regular maintainers
Signed-off-by: Daniel P. Berrangé <[email protected]>
Acked-by: Stefan Hajnoczi <[email protected]>
Acked-by: Peter Maydell <[email protected]>
Reviewed-by: Philippe Mathieu-Daudé <[email protected]>
Reviewed-by: Alex Bennée <[email protected]>
Acked-by: Richard Henderson <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Message-Id: <[email protected]>
Commit: c95309b221ebd6e240a62927836491a6a4a5d397
https://github.com/qemu/qemu/commit/c95309b221ebd6e240a62927836491a6a4a5d397
Author: Cédric Le Goater <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M tests/avocado/machine_aspeed.py
M tests/functional/meson.build
A tests/functional/test_aarch64_aspeed.py
Log Message:
-----------
tests/functional: Convert Aspeed aarch64 SDK tests
Drop the SSH connection which was introduced in the avocado tests to
workaround read issues when interacting with console.
Signed-off-by: Cédric Le Goater <[email protected]>
Reviewed-by: Thomas Huth <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Commit: f9ab0f467863a52445a37f36d7cf2dbd95db7553
https://github.com/qemu/qemu/commit/f9ab0f467863a52445a37f36d7cf2dbd95db7553
Author: Cédric Le Goater <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
R tests/avocado/machine_aspeed.py
M tests/functional/test_arm_aspeed.py
Log Message:
-----------
tests/functional: Convert Aspeed arm SDK tests
Drop the SSH connection which was introduced in the avocado tests to
workaround read issues when interacting with console.
EXTRA_BOOTARGS was introduced to reduce the console output at Linux
boot time. This didn't have the desired effect as we still had issues
when trying to match patterns on the console and we had to use the ssh
connection as a workaround.
While at it, remove the U-Boot EXTRA_BOOTARGS variable which has
become useless.
Signed-off-by: Cédric Le Goater <[email protected]>
Reviewed-by: Thomas Huth <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Commit: f8f5923808031e1335fc6d280a4b959ed5d28608
https://github.com/qemu/qemu/commit/f8f5923808031e1335fc6d280a4b959ed5d28608
Author: Cédric Le Goater <[email protected]>
Date: 2024-11-25 (Mon, 25 Nov 2024)
Changed paths:
M tests/functional/test_arm_aspeed.py
Log Message:
-----------
tests/functional: Remove sleep workarounds from Aspeed tests
These were introduced in the avocado tests to workaround read issues
when interacting with console. They are no longer necessary and we can
use the expected "login:" string or the command prompt now. Drop the
last use of exec_command.
Signed-off-by: Cédric Le Goater <[email protected]>
Reviewed-by: Thomas Huth <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Alex Bennée <[email protected]>
Commit: b8ee011e40e4b83a32ea0e7dca24e1ab089f1e7f
https://github.com/qemu/qemu/commit/b8ee011e40e4b83a32ea0e7dca24e1ab089f1e7f
Author: Peter Maydell <[email protected]>
Date: 2024-11-26 (Tue, 26 Nov 2024)
Changed paths:
M .gitlab-ci.d/check-dco.py
M MAINTAINERS
M docs/devel/submitting-a-patch.rst
M docs/devel/testing/functional.rst
M include/qemu/qemu-plugin.h
M plugins/meson.build
R plugins/qemu-plugins.symbols
M rust/hw/char/pl011/src/device.rs
A scripts/qemu-plugin-symbols.py
R tests/avocado/machine_aspeed.py
R tests/avocado/tuxrun_baselines.py
M tests/functional/meson.build
M tests/functional/qemu_test/cmd.py
M tests/functional/qemu_test/testcase.py
M tests/functional/qemu_test/tuxruntest.py
A tests/functional/test_aarch64_aspeed.py
A tests/functional/test_aarch64_tuxrun.py
M tests/functional/test_acpi_bits.py
M tests/functional/test_arm_aspeed.py
M tests/functional/test_arm_bpim2u.py
M tests/functional/test_arm_orangepi.py
M tests/functional/test_m68k_nextcube.py
M tests/functional/test_mips64el_malta.py
M tests/functional/test_virtio_gpu.py
Log Message:
-----------
Merge tag 'pull-9.2-rc2-updates-251124-1' of https://gitlab.com/stsquad/qemu
into staging
testing, docs and plugin updates for rc2
- cleanup leftover avocado bits from functional test
- ensure we keep functional logs for tests
- improve test console handling to detect prompts
- remove hacking timer.sleep() usage in functional tests
- convert Aarch64 tuxrun tests to functional test
- update Aarch64 tuxrun images to avoid corrupt blk I/O ops
- auto-generate the TCG plugin API symbols to avoid missing them
- fix rust pl011 model handling of DeviceID regs
- update docs to refer to "commonly known identity"
- convert aspeed tests to functional framework and remove hacky sleeps
# -----BEGIN PGP SIGNATURE-----
#
# iQEzBAABCgAdFiEEZoWumedRZ7yvyN81+9DbCVqeKkQFAmdEZXEACgkQ+9DbCVqe
# KkRdMAf+JoSdKn3ck/eji270bZ2Y3evgDuP/qOZlcBtUJJ7+bUvhEOnBMApwKRD8
# u63hz7M4LIV5k3mezlEADf+oEpZ2FR3nIDM0dTY2CXYZm6av+0dNV0qFhXwjkslk
# aqJLiJYgNl3wsyn/ftYNLiBhCid0sOGMvEOFZI6ELBh5KH8eiNdyrsaD0GSmpwZi
# BsZUi8TOKy6EBeWnco/FLBV8ZVZUHuHNBl84jUY/8g7cxGMJfK8KoqMJ5XYoiQoJ
# 1dYDqFmoP24iQRks6K6beFRdS/CBet36Nhsv7We/gf17Msw5uFo7Cho+touRCMrK
# AmVKFdOX/OqJAHqlEKquYAD7bPjpaA==
# =Xa/M
# -----END PGP SIGNATURE-----
# gpg: Signature made Mon 25 Nov 2024 11:54:25 GMT
# gpg: using RSA key 6685AE99E75167BCAFC8DF35FBD0DB095A9E2A44
# gpg: Good signature from "Alex Bennée (Master Work Key)
<[email protected]>" [full]
# Primary key fingerprint: 6685 AE99 E751 67BC AFC8 DF35 FBD0 DB09 5A9E 2A44
* tag 'pull-9.2-rc2-updates-251124-1' of https://gitlab.com/stsquad/qemu: (28
commits)
tests/functional: Remove sleep workarounds from Aspeed tests
tests/functional: Convert Aspeed arm SDK tests
tests/functional: Convert Aspeed aarch64 SDK tests
docs: explicitly permit a "commonly known identity" with SoB
rust/pl011: Fix range checks for device ID accesses
plugins: eradicate qemu-plugins.symbols static file
plugins: detect qemu plugin API symbols from header
plugins: add missing export for qemu_plugin_num_vcpus
tests/functional: update the aarch64 tuxrun tests
tests/functional: Convert the Avocado aarch64 tuxrun tests
tests/functional: avoid accessing log_filename on earlier failures
tests/functional: add a QMP backdoor for debugging stalled tests
tests/functional: remove time.sleep usage from tuxrun tests
tests/functional: rewrite console handling to be bytewise
tests/functional: require non-NULL success_message for console wait
tests/functional: don't try to wait for the empty string
tests/functional: logs details of console interaction operations
tests/functional: enable debug logging for QEMUMachine
tests/functional: honour requested test VM name in QEMUMachine
tests/functional: put QEMUMachine logs in testcase log directory
...
Signed-off-by: Peter Maydell <[email protected]>
Compare: https://github.com/qemu/qemu/compare/bd5629db935a...b8ee011e40e4
To unsubscribe from these emails, change your notification settings at
https://github.com/qemu/qemu/settings/notifications
