From: SeongJae Park <sj@kernel.org>
To: "Mohamed Abuelfotoh, Hazem" <abuehaze@amazon.com>
Cc: SeongJae Park <sj@kernel.org>,
shuah@kernel.org, keescook@chromium.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Vijaikumar_Kanagarajan@mentor.com,
brauner@kernel.org, jlayton@kernel.org, jack@suse.cz
Subject: Re: [PATCH] selftests/mqueue: Set timeout to 100 seconds
Date: Fri, 9 Feb 2024 09:42:43 -0800 [thread overview]
Message-ID: <20240209174243.74220-1-sj@kernel.org> (raw)
In-Reply-To: <4c17a7bb-c32c-4314-bd29-6d74b2413d54@amazon.com>
On Fri, 9 Feb 2024 10:30:38 +0000 "Mohamed Abuelfotoh, Hazem" <abuehaze@amazon.com> wrote:
> On 08/02/2024 21:29, SeongJae Park wrote:
> > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
> >
> >
> >
> > 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.
> >
> > 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>
> > ---
> > 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..54dc12287839
> > --- /dev/null
> > +++ b/tools/testing/selftests/mqueue/setting
> > @@ -0,0 +1 @@
> > +timeout=100
> > --
> > 2.39.2
> >
> >
>
> Added Vijai Kumar to CC
>
> This looks similar to [PATCH] kselftest: mqueue: increase timeout
> https://lore.kernel.org/lkml/20220622085911.2292509-1-Vijaikumar_Kanagarajan@mentor.com/T/#r12820aede6bba015b70ae33323e29ae27d5b69c7
> which was increasing the timeout to 180 however it's not clear why this
> hasn't been merged yet.
Thank you. I don't care who's patch would be picked, but hope any of those be
merged. For more eyes, I'm Cc-ing contacts from
`./scripts/get_maintainer.pl ipc/mqueue.c` output.
> I have seen the same issue on v5.15.y so it's
> very likely that we will need to apply this on all LTS branches not just
> 5.4 as mentioned in Cc: <stable@vger.kernel.org> # 5.4.x
Yes, that's the intent of the Fixes: and Cc: <stable@vger.kernel.org> lines. I
hope the lines to be added to Vijai's patch if it is picked instead of this.
Thanks,
SJ
>
> Hazem
>
next prev parent reply other threads:[~2024-02-09 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 21:29 [PATCH] selftests/mqueue: Set timeout to 100 seconds SeongJae Park
2024-02-09 10:30 ` Mohamed Abuelfotoh, Hazem
2024-02-09 17:42 ` SeongJae Park [this message]
2024-02-15 1:13 ` SeongJae Park
2024-02-17 0:01 ` Kees Cook
2024-02-17 0:31 ` SeongJae Park
2024-02-19 14:01 ` Mohamed Abuelfotoh, Hazem
2024-02-19 23:54 ` SeongJae Park
2024-02-19 15:06 ` Mohamed Abuelfotoh, Hazem
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=20240209174243.74220-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=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 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.