From: Shuah Khan <skhan@linuxfoundation.org>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Mark Brown" <broonie@kernel.org>
Cc: kernel@collabora.com, Jaroslav Kysela <perex@perex.cz>,
Shuah Khan <shuah@kernel.org>, Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] kselftest/alsa: Increase kselftest timeout
Date: Tue, 13 Dec 2022 11:37:56 -0700 [thread overview]
Message-ID: <2ee34e21-44bd-71e7-6da2-f4bea9a35452@linuxfoundation.org> (raw)
In-Reply-To: <20221213183242.1908249-1-nfraprado@collabora.com>
On 12/13/22 11:32, Nícolas F. R. A. Prado wrote:
> The default timeout for kselftests is 45 seconds, but pcm-test can take
> longer than that to run depending on the number of PCMs present on a
> device.
>
> As a data point, running pcm-test on mt8192-asurada-spherion takes about
> 1m15s.
>
> Set the timeout to 10 minutes, which should give enough slack to run the
> test even on devices with many PCMs.
>
10 minutes is way too long.
> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
>
> ---
>
> tools/testing/selftests/alsa/settings | 1 +
> 1 file changed, 1 insertion(+)
> create mode 100644 tools/testing/selftests/alsa/settings
>
> diff --git a/tools/testing/selftests/alsa/settings b/tools/testing/selftests/alsa/settings
> new file mode 100644
> index 000000000000..a62d2fa1275c
> --- /dev/null
> +++ b/tools/testing/selftests/alsa/settings
> @@ -0,0 +1 @@
> +timeout=600
Adding timeouts like this especially 10 minutes will increase the time
it takes to run tests. We run the risk of people not wanting to run tests
anymore.
thanks,
-- Shuah
next prev parent reply other threads:[~2022-12-13 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 18:32 Nícolas F. R. A. Prado
2022-12-13 18:36 ` Mark Brown
2022-12-13 18:37 ` Shuah Khan [this message]
2022-12-14 12:20 ` Nícolas F. R. A. Prado
2023-05-15 9:43 ` Ricardo Cañuelo
2023-06-16 7:10 ` Ricardo Cañuelo
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=2ee34e21-44bd-71e7-6da2-f4bea9a35452@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=nfraprado@collabora.com \
--cc=perex@perex.cz \
--cc=shuah@kernel.org \
--cc=tiwai@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 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®