Messages in this thread |  | | Date | Wed, 14 Dec 2022 09:40:02 -0700 | Subject | Re: [PATCH v2] kselftest/alsa: Increase kselftest timeout | From | Shuah Khan <> |
| |
On 12/14/22 06:03, Nícolas F. R. A. Prado wrote: > The default timeout for kselftests is 45 seconds, but that isn't enough > time to run pcm-test when there are many PCMs on the device, nor for > mixer-test when slower control buses and fancier CODECs are present. > > As data points, running pcm-test on mt8192-asurada-spherion takes about > 1m15s, and mixer-test on rk3399-gru-kevin takes about 2m. > > Set the timeout to 4 minutes to allow both pcm-test and mixer-test to > run to completion with some slack. > > Reviewed-by: Mark Brown <broonie@kernel.org> > Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com> > > --- > > Changes in v2: > - Reduced timeout from 10 to 4 minutes > - Tweaked commit message to also mention mixer-test and run time for > mixer-test on rk3399-gru-kevin >
What I have in mind is that the default run can be limited scope. Run it on a few controllers and in the report mention that a full test can be run as needed.
There are a couple of examples of default vs. full test runs - cpu and memory hot-lug tests.
thanks, -- Shuah
|  |