From: 李强 <liq3ea@163.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: pbonzini@redhat.com, thuth@redhat.com, lvivier@redhat.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] tests: fw_cfg: add reboot_timeout test case
Date: Tue, 30 Oct 2018 12:33:01 +0800 (CST) [thread overview]
Message-ID: <689cc088.f04a.166c33f0f26.Coremail.liq3ea@163.com> (raw)
In-Reply-To: <3a1b60e0-fe90-4da7-210e-4519f220bb9f@redhat.com>
At 2018-10-30 08:08:55, "Philippe Mathieu-Daudé" <philmd@redhat.com> wrote:
>On 28/10/18 13:40, Li Qiang wrote:
>> Signed-off-by: Li Qiang <liq3ea@163.com>
>> ---
>> tests/fw_cfg-test.c | 13 ++++++++++++-
>> 1 file changed, 12 insertions(+), 1 deletion(-)
>>
>> diff --git a/tests/fw_cfg-test.c b/tests/fw_cfg-test.c
>> index 1c5103fe1c..37765f15f8 100644
>> --- a/tests/fw_cfg-test.c
>> +++ b/tests/fw_cfg-test.c
>> @@ -99,6 +99,15 @@ static void test_fw_cfg_boot_menu(void)
>> g_assert_cmpint(qfw_cfg_get_u16(fw_cfg, FW_CFG_BOOT_MENU), ==, boot_menu);
>> }
>>
>> +static void test_fw_cfg_reboot_timeout(void)
>> +{
>> + uint32_t reboot_timeout;
>> +
>> + qfw_cfg_get_file(fw_cfg, "etc/boot-fail-wait",
>> + &reboot_timeout, sizeof(reboot_timeout));
>> + g_assert_cmpint(reboot_timeout, <=, 65535);
>> +}
>> +
>> int main(int argc, char **argv)
>> {
>> QTestState *s;
>> @@ -106,7 +115,8 @@ int main(int argc, char **argv)
>>
>> g_test_init(&argc, &argv, NULL);
>>
>> - s = qtest_init("-uuid 4600cb32-38ec-4b2f-8acb-81c6ea54f2d8");
>> + s = qtest_init("-uuid 4600cb32-38ec-4b2f-8acb-81c6ea54f2d8"
>> + " -boot reboot-timeout=4294967295");
>
>I'd rather change this test to use qtest_add_data_func() ...:
>
> qtest_add_data_func("fw_cfg/reboot_timeout", "-boot
>reboot-timeout=4294967295 ", test_fw_cfg_reboot_timeout);
>
Hi here I think use qtest_add_func is ok because there is no need
to make such an exception as all of them uses qtest_add_func.
Second, the uuid is also uses by all the cases though some of them are not needed.
Third, the -boot option will not affect the other cases.
Thanks,
Li Qiang
>... to avoid adding this command line option to all the tests, because
>all tests are now failing:
>
>$ make check-qtest-i386
>[...]
>ERROR:qemu/tests/fw_cfg-test.c:33:test_fw_cfg_signature: assertion
>failed (buf == "QEMU"): ("\377\377\377\377" == "QEMU")
>ERROR:qemu/tests/fw_cfg-test.c:40:test_fw_cfg_id: assertion failed: ((id
>== 1) || (id == 3))
>ERROR:qemu/tests/fw_cfg-test.c:52:test_fw_cfg_uuid: assertion failed:
>(memcmp(buf, uuid, sizeof(buf)) == 0)
>ERROR:qemu/tests/fw_cfg-test.c:57:test_fw_cfg_ram_size: assertion failed
>(qfw_cfg_get_u64(fw_cfg, FW_CFG_RAM_SIZE) == ram_size): (-1 == 134217728)
>ERROR:qemu/tests/fw_cfg-test.c:62:test_fw_cfg_nographic: assertion
>failed (qfw_cfg_get_u16(fw_cfg, FW_CFG_NOGRAPHIC) == 0): (65535 == 0)
>ERROR:qemu/tests/fw_cfg-test.c:67:test_fw_cfg_nb_cpus: assertion failed
>(qfw_cfg_get_u16(fw_cfg, FW_CFG_NB_CPUS) == nb_cpus): (65535 == 1)
>ERROR:qemu/tests/fw_cfg-test.c:72:test_fw_cfg_max_cpus: assertion failed
>(qfw_cfg_get_u16(fw_cfg, FW_CFG_MAX_CPUS) == max_cpus): (65535 == 1)
>ERROR:qemu/tests/fw_cfg-test.c:80:test_fw_cfg_numa: assertion failed
>(qfw_cfg_get_u64(fw_cfg, FW_CFG_NUMA) == nb_nodes): (-1 == 0)
>ERROR:qemu/tests/fw_cfg-test.c:99:test_fw_cfg_boot_menu: assertion
>failed (qfw_cfg_get_u16(fw_cfg, FW_CFG_BOOT_MENU) == boot_menu): (65535
>== 0)
>
>
>(did you test your patch?)
>
>>
>> fw_cfg = pc_fw_cfg_init(s);
>>
>> @@ -125,6 +135,7 @@ int main(int argc, char **argv)
>> qtest_add_func("fw_cfg/max_cpus", test_fw_cfg_max_cpus);
>> qtest_add_func("fw_cfg/numa", test_fw_cfg_numa);
>> qtest_add_func("fw_cfg/boot_menu", test_fw_cfg_boot_menu);
>> + qtest_add_func("fw_cfg/reboot_timeout", test_fw_cfg_reboot_timeout);
>>
>> ret = g_test_run();
>>
>>
next prev parent reply other threads:[~2018-10-30 4:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-28 12:40 [Qemu-devel] [PATCH 0/2] test: fw_cfg: add reboot-timeout test case Li Qiang
2018-10-28 12:40 ` [Qemu-devel] [PATCH 1/2] tests: fw_cfg: add a function to get the fw_cfg file entry Li Qiang
2018-10-29 23:46 ` Philippe Mathieu-Daudé
2018-10-30 1:45 ` li qiang
2018-10-28 12:40 ` [Qemu-devel] [PATCH 2/2] tests: fw_cfg: add reboot_timeout test case Li Qiang
2018-10-30 0:08 ` Philippe Mathieu-Daudé
2018-10-30 1:20 ` li qiang
2018-10-30 4:33 ` 李强 [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-20 7:13 [Qemu-devel] [PATCH 0/2] tests: fw_cfg: add reboot-timeout " Li Qiang
2019-01-20 7:13 ` [Qemu-devel] [PATCH 2/2] tests: fw_cfg: add reboot_timeout " Li Qiang
2019-01-21 21:38 ` Laszlo Ersek
2019-01-22 1:28 ` Li Qiang
2019-01-22 12:10 ` Laszlo Ersek
[not found] <20190319023030.947-1-liq3ea@163.com>
[not found] ` <20190319023030.947-3-liq3ea@163.com>
2019-04-18 21:01 ` Philippe Mathieu-Daudé
2019-04-18 21:01 ` Philippe Mathieu-Daudé
2019-04-19 2:23 ` Li Qiang
2019-04-19 2:23 ` Li Qiang
2019-04-20 10:07 ` Li Qiang
2019-04-20 10:07 ` Li Qiang
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=689cc088.f04a.166c33f0f26.Coremail.liq3ea@163.com \
--to=liq3ea@163.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).