selftests: arm64: sve-ptrace # TIMEOUT 45 seconds

selftests: arm64: sve-ptrace # TIMEOUT 45 seconds

[Naresh Kamboju]

While doing selftests: arm64 tests validations following test failed
due to shorter
timeout value.

Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>

not ok 28 selftests: arm64: sve-ptrace # TIMEOUT 45 seconds
not ok 35 selftests: arm64: check_gcr_el1_cswitch # TIMEOUT 45 seconds
not ok 40 selftests: arm64: check_user_mem # TIMEOUT 45 seconds

Test log link,
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.15.y/build/v5.15.78-131-g0963ae7afcba/testrun/13014345/suite/kselftest-arm64/test/arm64.check_user_mem/log

and
https://lkft.validation.linaro.org/scheduler/job/5847406


--
Linaro LKFT
https://lkft.linaro.org

Re: selftests: arm64: sve-ptrace # TIMEOUT 45 seconds

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]

On Wed, Nov 16, 2022 at 05:25:37PM +0530, Naresh Kamboju wrote:
> While doing selftests: arm64 tests validations following test failed
> due to shorter
> timeout value.
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> 
> not ok 28 selftests: arm64: sve-ptrace # TIMEOUT 45 seconds
> not ok 35 selftests: arm64: check_gcr_el1_cswitch # TIMEOUT 45 seconds
> not ok 40 selftests: arm64: check_user_mem # TIMEOUT 45 seconds

> and
> https://lkft.validation.linaro.org/scheduler/job/5847406

This appears to be the default timeout hard coded into the
kselftest runner, though that limit appears to be configurable.
Given that this report is for an emulated run on qemu rather than
a physical system I'd suggest you should be configuring a larger
limit, there does appear to be some support for that.

I do note that your system appears to be unusually slow even for
an emulated one, when I run sve-ptrace in qemu on my laptop I'm
seeing it taking about 10s which is vastly faster than 45s.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]