From: Avinesh Kumar <akumar@suse.de>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3] swapoff01/swapon01: Define max_runtime 1 mins
Date: Mon, 09 Sep 2024 13:05:15 +0200 [thread overview]
Message-ID: <2744588.vuYhMxLoTh@localhost> (raw)
In-Reply-To: <20240909025243.537071-1-liwang@redhat.com>
Hi,
Reviewed-by: Avinesh Kumar <akumar@suse.de>
On Monday, September 9, 2024 4:52:43 AM GMT+2 Li Wang wrote:
> From: Petr Vorel <pvorel@suse.cz>
>
> Test run mostly below 1 sec per filesystem, only NTFS is very slow
> ~ 10-15 sec depending on architecture.
>
> Also this is the only tests in syscalls which fails on due timeout on
> emulated risc-v with LTP_TIMEOUT_MUL=2,LTP_RUNTIME_MUL=2 (with the
> default 30s runtime => 1 min due LTP_RUNTIME_MUL=2).
>
> Based on the test consumed time on RPi0 and RPi4, we set runtime to 60s,
> that should be enough even for slow risc-v and not that high for other archs.
>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> Signed-off-by: Li Wang <liwang@redhat.com>
> ---
> testcases/kernel/syscalls/swapoff/swapoff01.c | 1 +
> testcases/kernel/syscalls/swapon/swapon01.c | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/testcases/kernel/syscalls/swapoff/swapoff01.c b/testcases/kernel/syscalls/swapoff/swapoff01.c
> index 314630267..965d17cc8 100644
> --- a/testcases/kernel/syscalls/swapoff/swapoff01.c
> +++ b/testcases/kernel/syscalls/swapoff/swapoff01.c
> @@ -53,5 +53,6 @@ static struct tst_test test = {
> .all_filesystems = 1,
> .needs_root = 1,
> .test_all = verify_swapoff,
> + .max_runtime = 60,
> .setup = setup
> };
> diff --git a/testcases/kernel/syscalls/swapon/swapon01.c b/testcases/kernel/syscalls/swapon/swapon01.c
> index 49915c32d..eddcd5788 100644
> --- a/testcases/kernel/syscalls/swapon/swapon01.c
> +++ b/testcases/kernel/syscalls/swapon/swapon01.c
> @@ -51,5 +51,6 @@ static struct tst_test test = {
> .all_filesystems = 1,
> .needs_cgroup_ctrls = (const char *const []){ "memory", NULL },
> .test_all = verify_swapon,
> + .max_runtime = 60,
> .setup = setup
> };
>
Regards,
Avinesh
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-09-09 11:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 14:03 [LTP] [PATCH v2 1/1] swapoff01: Define max_runtime 45s Petr Vorel
2024-09-03 15:15 ` Cyril Hrubis
2024-09-04 5:31 ` Petr Vorel
2024-09-04 8:52 ` Cyril Hrubis
2024-09-04 9:26 ` Li Wang
2024-09-04 9:37 ` Li Wang
2024-09-04 10:07 ` Petr Vorel
2024-09-04 13:58 ` Cyril Hrubis
2024-09-07 2:05 ` Li Wang
2024-09-09 2:52 ` [LTP] [PATCH v3] swapoff01/swapon01: Define max_runtime 1 mins Li Wang
2024-09-09 11:05 ` Avinesh Kumar [this message]
2024-09-09 11:46 ` Jan Stancek
2024-09-09 12:54 ` Cyril Hrubis
2024-09-09 14:02 ` 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=2744588.vuYhMxLoTh@localhost \
--to=akumar@suse.de \
--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.