From: Juan Quintela <quintela@redhat.com>
To: "Zhang, Chen" <chen.zhang@intel.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Thomas Huth" <thuth@redhat.com>, "John Snow" <jsnow@redhat.com>,
"Li Zhijian" <lizhijian@fujitsu.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>
Subject: Re: [PATCH v2 6/6] tests/migration: Only run auto_converge in slow mode
Date: Mon, 24 Apr 2023 07:58:11 +0200 [thread overview]
Message-ID: <87sfcpu8i4.fsf@secure.mitica> (raw)
In-Reply-To: <MWHPR11MB0031E5A085809AEAA22AFB519B669@MWHPR11MB0031.namprd11.prod.outlook.com> (Chen Zhang's message of "Sun, 23 Apr 2023 02:41:35 +0000")
"Zhang, Chen" <chen.zhang@intel.com> wrote:
>> -----Original Message-----
>> From: Daniel P. Berrangé <berrange@redhat.com>
>> Sent: Saturday, April 22, 2023 1:14 AM
>> To: qemu-devel@nongnu.org
>> Cc: qemu-block@nongnu.org; Paolo Bonzini <pbonzini@redhat.com>;
>> Thomas Huth <thuth@redhat.com>; John Snow <jsnow@redhat.com>; Li
>> Zhijian <lizhijian@fujitsu.com>; Juan Quintela <quintela@redhat.com>;
>> Stefan Hajnoczi <stefanha@redhat.com>; Zhang, Chen
>> <chen.zhang@intel.com>; Laurent Vivier <lvivier@redhat.com>
>> Subject: [PATCH v2 6/6] tests/migration: Only run auto_converge in slow
>> mode
>>
>
> What kind of scenario will the qtest open this g_test_init() -m slow to trigger the slow mode?
The only way that I know is:
export G_TEST_SLOW=1
make check (or whatever individual test that you want)
Later, Juan.
next prev parent reply other threads:[~2023-04-24 5:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 17:14 [PATCH v2 0/6] tests/qtest: make migration-test massively faster Daniel P. Berrangé
2023-04-21 17:14 ` [PATCH v2 1/6] tests/qtest: replace qmp_discard_response with qtest_qmp_assert_success Daniel P. Berrangé
2023-04-21 21:52 ` Juan Quintela
2023-04-23 2:22 ` Zhang, Chen
2023-04-21 17:14 ` [PATCH v2 2/6] tests/qtests: remove migration test iterations config Daniel P. Berrangé
2023-04-21 21:54 ` Juan Quintela
2023-04-26 9:07 ` Daniel P. Berrangé
2023-04-26 9:42 ` Juan Quintela
2023-04-26 10:15 ` Daniel P. Berrangé
2023-04-21 17:14 ` [PATCH v2 3/6] tests/qtest: capture RESUME events during migration Daniel P. Berrangé
2023-04-21 21:59 ` Juan Quintela
2023-04-24 9:53 ` Daniel P. Berrangé
2023-05-26 11:56 ` Daniel P. Berrangé
2023-04-21 17:14 ` [PATCH v2 4/6] tests/qtest: make more migration pre-copy scenarios run non-live Daniel P. Berrangé
2023-04-21 22:06 ` Juan Quintela
2023-04-24 21:01 ` Fabiano Rosas
2023-05-26 17:58 ` Daniel P. Berrangé
2023-05-31 12:15 ` Daniel P. Berrangé
2023-04-21 17:14 ` [PATCH v2 5/6] tests/qtest: massively speed up migration-tet Daniel P. Berrangé
2023-04-21 22:15 ` Juan Quintela
2023-04-21 17:14 ` [PATCH v2 6/6] tests/migration: Only run auto_converge in slow mode Daniel P. Berrangé
2023-04-23 2:41 ` Zhang, Chen
2023-04-24 5:58 ` Juan Quintela [this message]
2023-04-24 6:56 ` Thomas Huth
2023-04-24 8:05 ` Zhang, Chen
2023-04-24 8:06 ` Zhang, Chen
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=87sfcpu8i4.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=berrange@redhat.com \
--cc=chen.zhang@intel.com \
--cc=jsnow@redhat.com \
--cc=lizhijian@fujitsu.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).