From: Cyril Hrubis <chrubis@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it, Martin Doucha <martin.doucha@suse.com>
Subject: Re: [LTP] [PATCH V3] lib: redefine the overall timeout logic of test
Date: Fri, 10 Jan 2025 16:24:30 +0100 [thread overview]
Message-ID: <Z4E7rp-4x0LRay2H@yuki.lan> (raw)
In-Reply-To: <20250109130032.50480-1-liwang@redhat.com>
Hi!
> Notes:
> Changes V2 --> V3:
> * Improve timeout description based on Cyril's suggestion
> * Move .runtime to .timeout for some tests (fsplough, ksm02, ksm04)
> * Drop the changes on shell test test_timeout.sh
> * Squash tst_set_timeout and set_mempolicy01 patches into the first one
> * Double the duration of a single test iteration on an RPi4 and use that
> value to set .timeout for readahead02 test
Here you say timeout
> diff --git a/testcases/kernel/syscalls/readahead/readahead02.c b/testcases/kernel/syscalls/readahead/readahead02.c
> index a109573fe..412784dbb 100644
> --- a/testcases/kernel/syscalls/readahead/readahead02.c
> +++ b/testcases/kernel/syscalls/readahead/readahead02.c
> @@ -318,19 +318,6 @@ static void test_readahead(unsigned int n)
> tst_res(TCONF, "Page cache on your system is too small "
> "to hold whole testfile.");
> }
> -
> - /*
> - * The time consuming of readahead quite depending on the platform IO
> - * speed, sometime test timeout when the default max_runtime is used up.
> - *
> - * readahead02.c:221: TINFO: Test #2: POSIX_FADV_WILLNEED on file
> - * readahead02.c:285: TINFO: read_testfile(0) took: 26317623 usec
> - * readahead02.c:286: TINFO: read_testfile(1) took: 26101484 usec
> - *
> - * Here raise the maximum runtime dynamically.
> - */
> - if ((tc+1)->readahead)
> - tst_set_max_runtime(test.max_runtime + (usec + usec_ra) / 1000000);
> }
>
>
> @@ -381,7 +368,7 @@ static void setup(void)
> {
> if (opt_fsizestr) {
> testfile_size = SAFE_STRTOL(opt_fsizestr, 1, INT_MAX);
> - tst_set_max_runtime(1 + testfile_size / (DEFAULT_FILESIZE/32));
> + tst_set_runtime(1 + testfile_size / (DEFAULT_FILESIZE/32));
> }
>
> if (access(PROC_IO_FNAME, F_OK))
> @@ -422,7 +409,7 @@ static struct tst_test test = {
> },
> .test = test_readahead,
> .tcnt = ARRAY_SIZE(tcases),
> - .max_runtime = 30,
> + .runtime = 60,
But you actually set runtime instead.
> .tags = (const struct tst_tag[]) {
> {"linux-git", "b833a3660394"},
> {"linux-git", "5b910bd615ba"},
Otherwise:
Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2025-01-10 15:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 13:00 [LTP] [PATCH V3] lib: redefine the overall timeout logic of test Li Wang
2025-01-09 13:13 ` Li Wang
2025-01-10 17:13 ` Petr Vorel
2025-01-10 17:23 ` Petr Vorel
2025-01-13 10:22 ` Li Wang
2025-01-13 11:55 ` Cyril Hrubis
2025-01-13 2:47 ` Li Wang
2025-01-13 10:20 ` Li Wang
2025-01-13 12:08 ` Cyril Hrubis
2025-01-13 12:10 ` Petr Vorel
2025-01-10 15:24 ` Cyril Hrubis [this message]
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=Z4E7rp-4x0LRay2H@yuki.lan \
--to=chrubis@suse.cz \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
--cc=martin.doucha@suse.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 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.