From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 3/3] newlib_test: enable all tst_fuzzy_sync tests
Date: Thu, 2 Jan 2025 15:53:07 +0100 [thread overview]
Message-ID: <20250102145307.GD94207@pevik> (raw)
In-Reply-To: <20241222075102.14536-3-liwang@redhat.com>
Hi Li,
Reviewed-by: Petr Vorel <pvorel@suse.cz>
> Notes:
> This patch based on Peter's work:
> Message-ID: <20241210225753.381770-1-pvorel@suse.cz>
> CI: https://github.com/wangli5665/ltp/actions/runs/12452324779/
> lib/newlib_tests/runtest.sh | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
> diff --git a/lib/newlib_tests/runtest.sh b/lib/newlib_tests/runtest.sh
> index 66aaa9361..b00965b16 100755
> --- a/lib/newlib_tests/runtest.sh
> +++ b/lib/newlib_tests/runtest.sh
> @@ -2,7 +2,7 @@
> # Copyright (c) 2021-2024 Petr Vorel <pvorel@suse.cz>
> # TODO "unknown failure, exit code": test_assert test08 tst_cgroup01 tst_cgroup02 tst_res_flags variant
> -# TODO TFAIL: tst_fuzzy_sync01 tst_fuzzy_sync02 test_macros0[1-6] test23 test26
Ah, I should have mark it as tst_fuzzy_sync0[12]
Anyway, feel free to merge before I merge my patchset, I have no problem to
rebase mine.
Kind regards,
Petr
> +# TODO TFAIL: test_macros0[1-6] test23 test26
> # TODO TBROK: test_exec_child test_kconfig01 test_kconfig02 tst_needs_cmds04 tst_needs_cmds05 test_runtime02 test01 test02 test03 test04 test06 test11 test13 test22 test25 tst_safe_fileops
> # TODO TWARN: test_guarded_buf test14 tst_capability01 tst_print_result
> LTP_C_API_TESTS="${LTP_C_API_TESTS:-
> @@ -20,6 +20,8 @@ tst_bool_expr
> tst_capability02
> tst_device
> tst_expiration_timer
> +tst_fuzzy_sync01
> +tst_fuzzy_sync02
> tst_fuzzy_sync03
> tst_needs_cmds0[1-36-8]
> tst_res_hexd
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-01-02 14:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 7:51 [LTP] [PATCH 1/3] tst_fuzzy_sync: refine code and comment Li Wang
2024-12-22 7:51 ` [LTP] [PATCH 2/3] tst_fuzzy_sync: ingnore test result if loop termination occurs Li Wang
2025-01-02 14:50 ` Petr Vorel
2024-12-22 7:51 ` [LTP] [PATCH 3/3] newlib_test: enable all tst_fuzzy_sync tests Li Wang
2025-01-02 14:53 ` Petr Vorel [this message]
2025-01-02 14:38 ` [LTP] [PATCH 1/3] tst_fuzzy_sync: refine code and comment Petr Vorel
2025-01-02 14:41 ` Petr Vorel
2025-01-08 2:45 ` Li Wang
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=20250102145307.GD94207@pevik \
--to=pvorel@suse.cz \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.