From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Pavel Dovgalyuk <Pavel.Dovgaluk@gmail.com>, qemu-devel@nongnu.org
Cc: wrampazz@redhat.com, dovgaluk@ispras.ru,
pavel.dovgaluk@ispras.ru, crosa@redhat.com, pbonzini@redhat.com,
alex.bennee@linaro.org, ehabkost@redhat.com
Subject: Re: [PATCH v3 00/11] Record/replay acceptance tests
Date: Sun, 21 Jun 2020 01:36:35 +0200 [thread overview]
Message-ID: <343df8f4-9d26-bfce-a714-2d06940a2586@redhat.com> (raw)
In-Reply-To: <540831cc-c5b0-cf10-6889-bab499729a53@redhat.com>
Hi Pavel,
On 5/31/20 5:09 PM, Philippe Mathieu-Daudé wrote:
> On 5/29/20 9:04 AM, Pavel Dovgalyuk wrote:
>> 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.
>>
>> Tested-by: Philippe Mathieu-Daude <philmd@redhat.com>
>>
>> v3 changes:
>> - Added record/replay logging (suggested by Philippe Mathieu-Daudé)
>> - Changed the console pattern to get longer kernel execution (suggested by Alex Bennée)
>> - Coding style fixes
>> - Other minor changes
>> v2 changes:
>> - Some test structure refactoring (suggested by Willian Rampazzo)
>>
>> ---
>>
>> Pavel Dovgaluk (11):
>> tests/acceptance: allow console interaction with specific VMs
>> tests/acceptance: refactor boot_linux_console test to allow code reuse
>> 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
You forgot to Cc the maintainers for each target/machine tested.
Anyway this series has been on the list for 3 weeks, so I'm
queuing it for next acceptance-testing pull request.
Since the x86 tests generate some timeout errors on Travis-CI,
I squashed the following changes:
-- >8 --
diff --git a/tests/acceptance/replay_kernel.py
b/tests/acceptance/replay_kernel.py
index a25eb3d3ee..8fa6b517c5 100644
--- a/tests/acceptance/replay_kernel.py
+++ b/tests/acceptance/replay_kernel.py
@@ -12,6 +12,7 @@
import logging
import time
+from avocado import skipIf
from avocado_qemu import wait_for_console_pattern
from avocado.utils import archive
from avocado.utils import process
@@ -72,6 +73,7 @@ def run_rr(self, kernel_path, kernel_command_line,
console_pattern,
logger = logging.getLogger('replay')
logger.info('replay overhead {:.2%}'.format(t2 / t1 - 1))
+ @skipIf(os.getenv('CONTINUOUS_INTEGRATION'), 'Running on Travis-CI')
def test_x86_64_pc(self):
"""
:avocado: tags=arch:x86_64
diff --git a/tests/acceptance/replay_linux.py
b/tests/acceptance/replay_linux.py
index 472ab730cd..8e43e282a7 100644
--- a/tests/acceptance/replay_linux.py
+++ b/tests/acceptance/replay_linux.py
@@ -12,6 +12,7 @@
import logging
import time
+from avocado import skipIf
from avocado.utils import cloudinit
from avocado.utils import datadrainer
from avocado.utils import network
@@ -92,6 +93,7 @@ def run_rr(self, args=None, shift=7):
logger = logging.getLogger('replay')
logger.info('replay overhead {:.2%}'.format(t2 / t1 - 1))
+@skipIf(os.getenv('CONTINUOUS_INTEGRATION'), 'Running on Travis-CI')
class ReplayLinuxX8664(ReplayLinux):
"""
:avocado: tags=arch:x86_64
---
Regards,
Phil.
>> tests/acceptance: record/replay tests with advcal images
>> tests/acceptance: refactor boot_linux to allow code reuse
>> tests/acceptance: Linux boot test for record/replay
>
> Thanks, patches 1/2/10 applied to my python-next tree:
> https://gitlab.com/philmd/qemu/commits/python-next
>
> - tests/acceptance: allow console interaction with specific VMs
> - tests/acceptance: refactor boot_linux_console test to allow code reuse
> - tests/acceptance: refactor boot_linux to allow code reuse
>
next prev parent reply other threads:[~2020-06-20 23:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 7:04 [PATCH v3 00/11] Record/replay acceptance tests Pavel Dovgalyuk
2020-05-29 7:04 ` [PATCH v3 01/11] tests/acceptance: allow console interaction with specific VMs Pavel Dovgalyuk
2020-05-29 7:04 ` [PATCH v3 02/11] tests/acceptance: refactor boot_linux_console test to allow code reuse Pavel Dovgalyuk
2020-05-29 7:04 ` [PATCH v3 03/11] tests/acceptance: add base class record/replay kernel tests Pavel Dovgalyuk
2020-05-29 7:04 ` [PATCH v3 04/11] tests/acceptance: add kernel record/replay test for x86_64 Pavel Dovgalyuk
2020-05-29 7:05 ` [PATCH v3 05/11] tests/acceptance: add record/replay test for aarch64 Pavel Dovgalyuk
2020-05-29 7:05 ` [PATCH v3 06/11] tests/acceptance: add record/replay test for arm Pavel Dovgalyuk
2020-05-29 7:05 ` [PATCH v3 07/11] tests/acceptance: add record/replay test for ppc64 Pavel Dovgalyuk
2020-05-29 7:05 ` [PATCH v3 08/11] tests/acceptance: add record/replay test for m68k Pavel Dovgalyuk
2020-06-19 16:08 ` Laurent Vivier
2020-05-29 7:05 ` [PATCH v3 09/11] tests/acceptance: record/replay tests with advcal images Pavel Dovgalyuk
2020-06-21 11:51 ` Philippe Mathieu-Daudé
2020-05-29 7:05 ` [PATCH v3 10/11] tests/acceptance: refactor boot_linux to allow code reuse Pavel Dovgalyuk
2020-05-31 12:04 ` Philippe Mathieu-Daudé
2020-05-29 7:05 ` [PATCH v3 11/11] tests/acceptance: Linux boot test for record/replay Pavel Dovgalyuk
2020-06-22 8:03 ` Philippe Mathieu-Daudé
2020-06-22 8:54 ` Philippe Mathieu-Daudé
2020-05-31 15:09 ` [PATCH v3 00/11] Record/replay acceptance tests Philippe Mathieu-Daudé
2020-06-20 23:36 ` Philippe Mathieu-Daudé [this message]
2020-06-22 7:44 ` Pavel Dovgalyuk
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=343df8f4-9d26-bfce-a714-2d06940a2586@redhat.com \
--to=philmd@redhat.com \
--cc=Pavel.Dovgaluk@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=dovgaluk@ispras.ru \
--cc=ehabkost@redhat.com \
--cc=pavel.dovgaluk@ispras.ru \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wrampazz@redhat.com \
/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).