From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>
Subject: [PULL 0/6] gdbstub, avocado and gitlab updates
Date: Fri, 1 Dec 2023 15:12:22 +0000 [thread overview]
Message-ID: <20231201151228.2610209-1-alex.bennee@linaro.org> (raw)
The following changes since commit abf635ddfe3242df907f58967f3c1e6763bbca2d:
Update version for v8.2.0-rc2 release (2023-11-28 16:31:16 -0500)
are available in the Git repository at:
https://gitlab.com/stsquad/qemu.git tags/pull-more-8.2-fixes-011223-1
for you to fetch changes up to a7a740cce1ec49568e7ebd8e776279e59e2fb5b6:
gitlab: add optional job to run flaky avocado tests (2023-12-01 14:12:05 +0000)
----------------------------------------------------------------
Flaky avocado tests, gdbstub and gitlab tweaks
- gdbstub, properly halt when QEMU is having IO issues
- convert skipIf(GITLAB_CI) to skipUnless(QEMU_TEST_FLAKY_TESTS)
- drop mips malta cpio test as assets expire in Debian archive
- tag sbsa-ref tests as TCG only
- build the correct microblaze for avocado-system-ubuntu
- add optional flaky tests job to CI
----------------------------------------------------------------
Alex Bennée (6):
gdbstub: use a better signal when we halt for IO reasons
docs/devel: rationalise unstable gitlab tests under FLAKY_TESTS
tests/avocado: drop BootLinuxConsole.test_mips_malta_cpio test
tests/avocado: tag sbsa tests as tcg only
gitlab: build the correct microblaze target
gitlab: add optional job to run flaky avocado tests
docs/devel/testing.rst | 32 ++++++++++++++--------
gdbstub/internals.h | 1 +
gdbstub/system.c | 2 +-
.gitlab-ci.d/buildtest.yml | 32 +++++++++++++++++++++-
tests/avocado/boot_linux.py | 10 +++++--
tests/avocado/boot_linux_console.py | 47 +++-----------------------------
tests/avocado/intel_iommu.py | 6 ++--
tests/avocado/linux_initrd.py | 7 +++--
tests/avocado/machine_aarch64_sbsaref.py | 4 +++
tests/avocado/machine_aspeed.py | 10 +++++--
tests/avocado/machine_mips_malta.py | 10 +++++--
tests/avocado/machine_rx_gdbsim.py | 10 +++++--
tests/avocado/machine_s390_ccw_virtio.py | 3 +-
tests/avocado/replay_kernel.py | 8 ++++--
tests/avocado/reverse_debugging.py | 16 +++++++----
tests/avocado/smmu.py | 6 ++--
tests/avocado/tuxrun_baselines.py | 5 ++--
17 files changed, 125 insertions(+), 84 deletions(-)
--
2.39.2
next reply other threads:[~2023-12-01 15:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 15:12 Alex Bennée [this message]
2023-12-01 15:12 ` [PULL 1/6] gdbstub: use a better signal when we halt for IO reasons Alex Bennée
2023-12-01 15:12 ` [PULL 2/6] docs/devel: rationalise unstable gitlab tests under FLAKY_TESTS Alex Bennée
2023-12-01 15:12 ` [PULL 3/6] tests/avocado: drop BootLinuxConsole.test_mips_malta_cpio test Alex Bennée
2023-12-01 16:49 ` Philippe Mathieu-Daudé
2023-12-01 17:46 ` Alex Bennée
2023-12-01 15:12 ` [PULL 4/6] tests/avocado: tag sbsa tests as tcg only Alex Bennée
2023-12-01 15:12 ` [PULL 5/6] gitlab: build the correct microblaze target Alex Bennée
2023-12-01 15:12 ` [PULL 6/6] gitlab: add optional job to run flaky avocado tests Alex Bennée
2023-12-01 16:50 ` [PULL 0/6] gdbstub, avocado and gitlab updates Philippe Mathieu-Daudé
2023-12-01 16:52 ` Philippe Mathieu-Daudé
2023-12-01 17:50 ` Alex Bennée
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=20231201151228.2610209-1-alex.bennee@linaro.org \
--to=alex.bennee@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 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).