From: Fabiano Rosas <farosas@suse.de>
To: quintela@redhat.com
Cc: qemu-devel@nongnu.org, "Peter Xu" <peterx@redhat.com>,
"Leonardo Bras" <leobras@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH v2 6/6] tests/qtest/migration: Add a test for the analyze-migration script
Date: Wed, 11 Oct 2023 10:35:11 -0300 [thread overview]
Message-ID: <87mswp1dv4.fsf@suse.de> (raw)
In-Reply-To: <87mswp9tkp.fsf@secure.mitica>
Juan Quintela <quintela@redhat.com> writes:
> Fabiano Rosas <farosas@suse.de> wrote:
>> Add a smoke test that migrates to a file and gives it to the
>> script. It should catch the most annoying errors such as changes in
>> the ram flags.
>>
>> After code has been merged it becomes way harder to figure out what is
>> causing the script to fail, the person making the change is the most
>> likely to know right away what the problem is.
>>
>> Signed-off-by: Fabiano Rosas <farosas@suse.de>
>
> Reviewed-by: Juan Quintela <quintela@redhat.com>
>
>
>> ---
>> tests/qtest/meson.build | 2 ++
>> tests/qtest/migration-test.c | 60 ++++++++++++++++++++++++++++++++++++
>> 2 files changed, 62 insertions(+)
>>
>> diff --git a/tests/qtest/meson.build b/tests/qtest/meson.build
>> index 1fba07f4ed..5e82eccb62 100644
>> --- a/tests/qtest/meson.build
>> +++ b/tests/qtest/meson.build
>> @@ -356,6 +356,8 @@ foreach dir : target_dirs
>> test_deps += [qsd]
>> endif
>>
>> + qtest_env.set('PYTHON', python.full_path())
>> +
>
> I accept it, but I think that this part of the test should be in a
> different patch so meson people could comment O:-)
>
>> +
>> + pid = fork();
>
> live and see, g_test and qemu don't have a function to execute a script?
gtest has one to execute a _function_ in a fork, but fork+exec no.
next prev parent reply other threads:[~2023-10-11 13:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 18:43 [PATCH v2 0/6] scripts/migration: Fix analyze-migration.py and add a test Fabiano Rosas
2023-10-09 18:43 ` [PATCH v2 1/6] migration: Add the configuration vmstate to the json writer Fabiano Rosas
2023-10-11 13:12 ` Juan Quintela
2023-10-11 13:33 ` Fabiano Rosas
2023-10-09 18:43 ` [PATCH v2 2/6] migration: Fix analyze-migration.py 'configuration' parsing Fabiano Rosas
2023-10-11 13:16 ` Juan Quintela
2023-10-09 18:43 ` [PATCH v2 3/6] migration: Add capability parsing to analyze-migration.py Fabiano Rosas
2023-10-11 13:22 ` Juan Quintela
2023-10-09 18:43 ` [PATCH v2 4/6] migration: Fix analyze-migration.py when ignore-shared is used Fabiano Rosas
2023-10-11 13:23 ` Juan Quintela
2023-10-11 13:32 ` Fabiano Rosas
2023-10-11 14:10 ` Juan Quintela
2023-10-09 18:43 ` [PATCH v2 5/6] migration: Fix analyze-migration read operation signedness Fabiano Rosas
2023-10-11 13:24 ` Juan Quintela
2023-10-09 18:43 ` [PATCH v2 6/6] tests/qtest/migration: Add a test for the analyze-migration script Fabiano Rosas
2023-10-10 7:11 ` Thomas Huth
2023-10-11 13:28 ` Juan Quintela
2023-10-11 13:35 ` Fabiano Rosas [this message]
2023-10-10 20:27 ` [PATCH v2 0/6] scripts/migration: Fix analyze-migration.py and add a test Fabiano Rosas
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=87mswp1dv4.fsf@suse.de \
--to=farosas@suse.de \
--cc=leobras@redhat.com \
--cc=lvivier@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=thuth@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).