From: Pavel Dovgalyuk <Pavel.Dovgaluk@gmail.com>
To: qemu-devel@nongnu.org
Cc: philmd@redhat.com, dovgaluk@ispras.ru, pavel.dovgaluk@ispras.ru,
crosa@redhat.com, pbonzini@redhat.com, alex.bennee@linaro.org
Subject: [PATCH 0/9] Record/replay acceptance tests
Date: Mon, 25 May 2020 14:19:02 +0300 [thread overview]
Message-ID: <159040554265.2615.8993443700754452381.stgit@pasha-ThinkPad-X280> (raw)
The following series adds record/replay tests to the acceptance group.
Test pass successfully with the latest submitted record/replay fixes:
- replay: notify the main loop when there are no instructions
- replay: synchronize on every virtual timer callback
The provided tests perform kernel boot and disk image boot scenarios.
For all of them recording and replaying phases are executed.
Tests were borrowed from existing boot_linux*.py tests. But some
of the platforms and images were excluded, because icount for them
still has some issues.
---
Pavel Dovgaluk (9):
tests/acceptance: allow console interaction with specific VMs
tests/acceptance: add base class record/replay kernel tests
tests/acceptance: add kernel record/replay test for x86_64
tests/acceptance: add record/replay test for aarch64
tests/acceptance: add record/replay test for arm
tests/acceptance: add record/replay test for ppc64
tests/acceptance: add record/replay test for m68k
tests/acceptance: record/replay tests with advcal images
tests/acceptance: Linux boot test for record/replay
MAINTAINERS | 2
tests/acceptance/avocado_qemu/__init__.py | 12 +
tests/acceptance/replay_kernel.py | 273 +++++++++++++++++++++++++++++
tests/acceptance/replay_linux.py | 140 +++++++++++++++
4 files changed, 422 insertions(+), 5 deletions(-)
create mode 100644 tests/acceptance/replay_kernel.py
create mode 100644 tests/acceptance/replay_linux.py
--
Pavel Dovgalyuk
next reply other threads:[~2020-05-25 11:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 11:19 Pavel Dovgalyuk [this message]
2020-05-25 11:19 ` [PATCH 1/9] tests/acceptance: allow console interaction with specific VMs Pavel Dovgalyuk
2020-05-26 20:48 ` Willian Rampazzo
2020-05-25 11:19 ` [PATCH 2/9] tests/acceptance: add base class record/replay kernel tests Pavel Dovgalyuk
2020-05-26 20:46 ` Willian Rampazzo
2020-05-25 11:19 ` [PATCH 3/9] tests/acceptance: add kernel record/replay test for x86_64 Pavel Dovgalyuk
2020-05-25 11:19 ` [PATCH 4/9] tests/acceptance: add record/replay test for aarch64 Pavel Dovgalyuk
2020-05-25 11:19 ` [PATCH 5/9] tests/acceptance: add record/replay test for arm Pavel Dovgalyuk
2020-05-25 11:19 ` [PATCH 6/9] tests/acceptance: add record/replay test for ppc64 Pavel Dovgalyuk
2020-05-25 11:19 ` [PATCH 7/9] tests/acceptance: add record/replay test for m68k Pavel Dovgalyuk
2020-05-25 11:19 ` [PATCH 8/9] tests/acceptance: record/replay tests with advcal images Pavel Dovgalyuk
2020-05-26 19:22 ` Willian Rampazzo
2020-05-25 11:19 ` [PATCH 9/9] tests/acceptance: Linux boot test for record/replay Pavel Dovgalyuk
2020-05-26 19:06 ` Willian Rampazzo
2020-05-26 19:52 ` Willian Rampazzo
2020-05-25 17:03 ` [PATCH 0/9] Record/replay acceptance tests no-reply
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=159040554265.2615.8993443700754452381.stgit@pasha-ThinkPad-X280 \
--to=pavel.dovgaluk@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=dovgaluk@ispras.ru \
--cc=pavel.dovgaluk@ispras.ru \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--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).