qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Pavel Dovgalyuk <dovgaluk@ispras.ru>
Cc: wrampazz@redhat.com, qemu-devel@nongnu.org,
	Pavel Dovgalyuk <Pavel.Dovgaluk@gmail.com>,
	pavel.dovgaluk@ispras.ru, crosa@redhat.com, pbonzini@redhat.com,
	philmd@redhat.com
Subject: Re: [PATCH v2 04/11] tests/acceptance: add kernel record/replay test for x86_64
Date: Fri, 29 May 2020 10:20:55 +0100	[thread overview]
Message-ID: <87v9kf2j2g.fsf@linaro.org> (raw)
In-Reply-To: <f9906fce-55fd-1fe2-0a9b-ff5d8d91c0fa@ispras.ru>

[-- Attachment #1: Type: text/plain, Size: 1794 bytes --]


Pavel Dovgalyuk <dovgaluk@ispras.ru> writes:

> On 28.05.2020 16:26, Alex Bennée wrote:
>> Pavel Dovgalyuk <dovgaluk@ispras.ru> writes:
>>
>>> On 27.05.2020 18:41, Alex Bennée wrote:
>>>> Pavel Dovgalyuk <Pavel.Dovgaluk@gmail.com> writes:
>>>>
>>>>> This patch adds a test for record/replay an execution of x86_64 machine.
>>>>> Execution scenario includes simple kernel boot, which allows testing
>>>>> basic hardware interaction in RR mode.
<snip>
>>>> This test fails for me on the replay:
>>> Have you applied latest RR patches?
>> I have the following on top of the acceptance patches:
>>
>> a36c23042fe * review/record-replay-acceptance-v2 icount: fix shift=auto for record/replay
>> 4ab2164c10b * replay: synchronize on every virtual timer callback
>> 66104ce6e4b * replay: notify the main loop when there are no instructions
>>
> Please also try adding "replay: implement fair mutex"

OK that was enough to get the pc_i440fx to pass:

  JOB ID     : 33f94542f1f2d1e98c8dad820f66ec5ea9bd9fc1
  JOB LOG    : /home/alex/avocado/job-results/job-2020-05-29T09.36-33f9454/job.log
   (1/2) ./tests/acceptance/replay_linux.py:ReplayLinuxX8664.test_pc_i440fx: PASS (502.55 s)
   (2/2) ./tests/acceptance/replay_linux.py:ReplayLinuxX8664.test_pc_q35: INTERRUPTED: Test died without reporting the status.\nRunner error occurred: Timeout reached\nOriginal status: ERROR\n{'name': '2-./tests/acceptance/replay_linux.py:ReplayLinuxX8664.test_pc_q35', 'logdir': '/home/alex/avocado/job-results/job-2020-05-29T09.36-33f9454/test... (1811.23 s)
  RESULTS    : PASS 1 | ERROR 0 | FAIL 0 | SKIP 0 | WARN 0 | INTERRUPT 1 | CANCEL 0
  JOB TIME   : 2313.96 s

I've attached the log although it's a bit messy because the console
seems to have stripped out any newlines.


[-- Attachment #2: log file of failure --]
[-- Type: application/octet-stream, Size: 585179 bytes --]

[-- Attachment #3: Type: text/plain, Size: 23 bytes --]



-- 
Alex Bennée

  reply	other threads:[~2020-05-29  9:23 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27 10:30 [PATCH v2 00/11] Record/replay acceptance tests Pavel Dovgalyuk
2020-05-27 10:30 ` [PATCH v2 01/11] tests/acceptance: allow console interaction with specific VMs Pavel Dovgalyuk
2020-05-27 14:20   ` Alex Bennée
2020-05-27 14:42     ` Willian Rampazzo
2020-05-27 10:30 ` [PATCH v2 02/11] tests/acceptance: refactor boot_linux_console test to allow code reuse Pavel Dovgalyuk
2020-05-27 14:31   ` Alex Bennée
2020-05-27 10:30 ` [PATCH v2 03/11] tests/acceptance: add base class record/replay kernel tests Pavel Dovgalyuk
2020-05-27 14:41   ` Philippe Mathieu-Daudé
2020-05-27 15:20   ` Alex Bennée
2020-05-28  7:19     ` Pavel Dovgalyuk
2020-05-28  8:28       ` Alex Bennée
2020-05-29  5:58         ` Pavel Dovgalyuk
2020-05-27 10:31 ` [PATCH v2 04/11] tests/acceptance: add kernel record/replay test for x86_64 Pavel Dovgalyuk
2020-05-27 14:53   ` Philippe Mathieu-Daudé
2020-05-28  7:12     ` Pavel Dovgalyuk
2020-05-28  8:38       ` Philippe Mathieu-Daudé
2020-05-28 11:07         ` Alex Bennée
2020-05-28 11:32           ` Philippe Mathieu-Daudé
2020-05-27 15:40   ` Alex Bennée
2020-05-27 16:20     ` Alex Bennée
2020-05-28  7:26       ` Pavel Dovgalyuk
2020-05-27 15:41   ` Alex Bennée
2020-05-28  6:12     ` Pavel Dovgalyuk
2020-05-28 13:26       ` Alex Bennée
2020-05-29  5:56         ` Pavel Dovgalyuk
2020-05-29  9:20           ` Alex Bennée [this message]
2020-05-27 10:31 ` [PATCH v2 05/11] tests/acceptance: add record/replay test for aarch64 Pavel Dovgalyuk
2020-05-27 14:44   ` Philippe Mathieu-Daudé
2020-05-27 10:31 ` [PATCH v2 06/11] tests/acceptance: add record/replay test for arm Pavel Dovgalyuk
2020-05-27 10:31 ` [PATCH v2 07/11] tests/acceptance: add record/replay test for ppc64 Pavel Dovgalyuk
2020-05-27 10:31 ` [PATCH v2 08/11] tests/acceptance: add record/replay test for m68k Pavel Dovgalyuk
2020-05-27 10:31 ` [PATCH v2 09/11] tests/acceptance: record/replay tests with advcal images Pavel Dovgalyuk
2020-05-27 10:31 ` [PATCH v2 10/11] tests/acceptance: refactor boot_linux to allow code reuse Pavel Dovgalyuk
2020-05-27 10:31 ` [PATCH v2 11/11] tests/acceptance: Linux boot test for record/replay Pavel Dovgalyuk
2020-05-27 16:44   ` Alex Bennée
2020-05-28  6:17     ` Pavel Dovgalyuk
2020-05-27 13:41 ` [PATCH v2 00/11] Record/replay acceptance tests no-reply
2020-05-27 14:53   ` Philippe Mathieu-Daudé

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=87v9kf2j2g.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=Pavel.Dovgaluk@gmail.com \
    --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 \
    --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).