From: SeongJae Park <sj@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: shuah@kernel.org, ryan.roberts@arm.com, abuehaze@amazon.com,
brauner@kernel.org, jlayton@kernel.org, jack@suse.cz,
keescook@chromium.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Vijaikumar_Kanagarajan@mentor.com
Subject: Re: [PATCH v2] selftests/mqueue: Set timeout to 180 seconds
Date: Mon, 19 Feb 2024 16:06:15 -0800 [thread overview]
Message-ID: <20240220000615.162512-1-sj@kernel.org> (raw)
In-Reply-To: <20240220000243.162285-1-sj@kernel.org>
On Mon, 19 Feb 2024 16:02:43 -0800 SeongJae Park <sj@kernel.org> wrote:
> While mq_perf_tests runs with the default kselftest timeout limit, which
> is 45 seconds, the test takes about 60 seconds to complete on i3.metal
> AWS instances. Hence, the test always times out. Increase the timeout
> to 100 seconds.
Oops, I forgot updating this message.
>
> Link: https://lore.kernel.org/r/20240208212925.68286-1-sj@kernel.org
Also, this Link: line should be removed.
I will send v3 with above fixes.
Thanks,
SJ
> Fixes: 852c8cbf34d3 ("selftests/kselftest/runner.sh: Add 45 second timeout per test")
> Cc: <stable@vger.kernel.org> # 5.4.x
> Signed-off-by: SeongJae Park <sj@kernel.org>
> Reviewed-by: Kees Cook <keescook@chromium.org>
> ---
> Changes from v1
> (https://lore.kernel.org/r/20240208212925.68286-1-sj@kernel.org)
> - Use 180 seconds timeout instead of 100 seconds
>
> tools/testing/selftests/mqueue/setting | 1 +
> 1 file changed, 1 insertion(+)
> create mode 100644 tools/testing/selftests/mqueue/setting
>
> diff --git a/tools/testing/selftests/mqueue/setting b/tools/testing/selftests/mqueue/setting
> new file mode 100644
> index 000000000000..a953c96aa16e
> --- /dev/null
> +++ b/tools/testing/selftests/mqueue/setting
> @@ -0,0 +1 @@
> +timeout=180
> --
> 2.39.2
prev parent reply other threads:[~2024-02-20 0:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 0:02 [PATCH v2] selftests/mqueue: Set timeout to 180 seconds SeongJae Park
2024-02-20 0:06 ` SeongJae Park [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=20240220000615.162512-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=Vijaikumar_Kanagarajan@mentor.com \
--cc=abuehaze@amazon.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
/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