From: Mark Brown <broonie@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: "open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org, Shuah Khan <shuah@kernel.org>,
Kees Cook <keescook@chromium.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: selftests: arm64: sve-ptrace # TIMEOUT 45 seconds
Date: Wed, 16 Nov 2022 14:41:58 +0000 [thread overview]
Message-ID: <Y3T2ts+7I8g62hOM@sirena.org.uk> (raw)
In-Reply-To: <CA+G9fYu8grBstgXDsC_g5tmEg0nVwaQ+p0d6vD+mN7UsTvMCSQ@mail.gmail.com>
[-- 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 --]
prev parent reply other threads:[~2022-11-16 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 11:55 Naresh Kamboju
2022-11-16 14:41 ` Mark Brown [this message]
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=Y3T2ts+7I8g62hOM@sirena.org.uk \
--to=broonie@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--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®