mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Yun Lu <luyun@kylinos.cn>,
	jikos@kernel.org, bentiss@kernel.org, shuah@kernel.org
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftest/hid: increase timeout to 10 min
Date: Tue, 29 Oct 2024 19:11:58 -0600	[thread overview]
Message-ID: <85570e57-1af3-4d17-8a21-58c75e6bac9c@linuxfoundation.org> (raw)
In-Reply-To: <20241029090746.179108-1-luyun@kylinos.cn>

On 10/29/24 03:07, Yun Lu wrote:
> If running hid testcases with command "./run_kselftest.sh -c hid",

NIT - When inestead of "If"
> the following tests will take longer than the kselftest framework
> timeout (now 200 seconds) to run and thus got terminated with TIMEOUT
> error:
> 
>    hid-multitouch.sh - took about 6min41s
>    hid-tablet.sh - took about 6min30s
> 
> Increase the timeout setting to 10 minutes to allow them have a chance
> to finish.
> 
> Cc: stable@vger.kernel.org
> Signed-off-by: Yun Lu <luyun@kylinos.cn>
> ---
>   tools/testing/selftests/hid/settings | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/testing/selftests/hid/settings b/tools/testing/selftests/hid/settings
> index b3cbfc521b10..dff0d947f9c2 100644
> --- a/tools/testing/selftests/hid/settings
> +++ b/tools/testing/selftests/hid/settings
> @@ -1,3 +1,3 @@
>   # HID tests can be long, so give a little bit more time
>   # to them
> -timeout=200
> +timeout=600

Okay - maybe this test shouldn't be part of the default run if it needs
600 seconds to run?

thanks,
-- Shuah

  reply	other threads:[~2024-10-30  1:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29  9:07 Yun Lu
2024-10-30  1:11 ` Shuah Khan [this message]
2024-10-30  8:00   ` Benjamin Tissoires

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=85570e57-1af3-4d17-8a21-58c75e6bac9c@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=bentiss@kernel.org \
    --cc=jikos@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=luyun@kylinos.cn \
    --cc=shuah@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

all inboxes | Powered by JetHome®