From: Peter Xu <peterx@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>,
Leonardo Bras <leobras@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v1 5/7] tests/qtest/migration: Print migration incoming errors
Date: Mon, 27 Nov 2023 15:23:00 -0500 [thread overview]
Message-ID: <ZWT6pCri-NmPy3Bt@x1n> (raw)
In-Reply-To: <87ttp72ny1.fsf@suse.de>
On Mon, Nov 27, 2023 at 12:52:38PM -0300, Fabiano Rosas wrote:
> >> @@ -118,6 +118,12 @@ void migrate_incoming_qmp(QTestState *to, const char *uri, const char *fmt, ...)
> >>
> >> rsp = qtest_qmp(to, "{ 'execute': 'migrate-incoming', 'arguments': %p}",
> >> args);
> >> +
> >> + if (!qdict_haskey(rsp, "return")) {
> >> + g_autoptr(GString) s = qobject_to_json_pretty(QOBJECT(rsp), true);
> >> + g_test_message("%s", s->str);
> >> + }
> >
> > This traps the "migrate-incoming" command only (which, afaiu, only setup
> > the listening), would this capture the incoming error?
>
> This is about the migrate-incoming only. We could replace "incoming
> migration" with "qmp_migrate_incoming" in the commit message to clarify.
Ah.. Did you ever see this failure in any of your runs in these tests? I
think it means you hit the assertion right below this part, but I'm just
curious how, as the URIs in the test cases are pretty constant.
--
Peter Xu
next prev parent reply other threads:[~2023-11-27 20:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 16:14 [PATCH v1 0/7] migration cleanups and testing improvements Fabiano Rosas
2023-11-24 16:14 ` [PATCH v1 1/7] migration/multifd: Remove MultiFDPages_t::packet_num Fabiano Rosas
2023-11-27 14:42 ` Peter Xu
2023-11-24 16:14 ` [PATCH v1 2/7] migration/multifd: Remove QEMUFile from where it is not needed Fabiano Rosas
2023-11-27 14:44 ` Peter Xu
2023-11-24 16:14 ` [PATCH v1 3/7] migration/multifd: Change multifd_pages_init argument Fabiano Rosas
2023-11-27 14:45 ` Peter Xu
2023-11-24 16:14 ` [PATCH v1 4/7] migration: Report error in incoming migration Fabiano Rosas
2023-11-27 14:46 ` Peter Xu
2023-11-24 16:14 ` [PATCH v1 5/7] tests/qtest/migration: Print migration incoming errors Fabiano Rosas
2023-11-27 14:50 ` Peter Xu
2023-11-27 15:52 ` Fabiano Rosas
2023-11-27 20:23 ` Peter Xu [this message]
2023-11-27 20:32 ` Fabiano Rosas
2023-11-27 20:52 ` Peter Xu
2023-11-24 16:14 ` [PATCH v1 6/7] tests/qtest/migration: Add a wrapper to print test names Fabiano Rosas
2023-11-27 14:54 ` Peter Xu
2023-11-27 15:44 ` Fabiano Rosas
2023-11-27 15:56 ` Peter Xu
2023-11-24 16:14 ` [PATCH v1 7/7] tests/qtest/migration: Use the new migration_test_add Fabiano Rosas
2023-11-27 14:55 ` Peter Xu
2024-01-04 4:56 ` [PATCH v1 0/7] migration cleanups and testing improvements Peter Xu
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=ZWT6pCri-NmPy3Bt@x1n \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--cc=leobras@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@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).