From: Tim Lewis <elatllat@gmail.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: Re: [PATCH 5.10 000/578] 5.10.80-rc2 review
Date: Thu, 18 Nov 2021 10:37:46 -0500 [thread overview]
Message-ID: <CA+3zgmtwFQNc05why_bT1fXxPM2ShHtZ=MaB6QOmkYw81wKn6A@mail.gmail.com> (raw)
In-Reply-To: <CA+G9fYuFqFyYXkvGK8jVCZAiDZW_oNG4dNY_2q9BG__uXRR1DQ@mail.gmail.com>
On Thu, Nov 18, 2021 at 5:41 AM Naresh Kamboju
<naresh.kamboju@linaro.org> wrote:
...
> I have noticed intermittent failures on slow devices.
...
> When the test runs more than X time (45 sec i guess) the script will
> be killed by the runner script.
In my test environment proc-uptime-001 seems to be passing ~40% (N=10)
of the time,
and taking approximately 0.60 seconds (~11 seconds / 18 tests).
kselftest is not timing individual targets (maybe it should?),
so I don't have a timing history but it used to pass 100% (N=60) of the time.
> We will add this as known intermittent failure.
Thanks, I'll remove it from my tests.
Data for the numbers above:
for X in $(seq 1 10) ; do echo $X && time make TARGETS="proc"
kselftest | grep -P "ok.*proc-uptime-001" ; done
1
ok 10 selftests: proc: proc-uptime-001
real 0m10.605s
user 0m3.427s
sys 0m7.239s
2
not ok 10 selftests: proc: proc-uptime-001 # exit=134
real 0m10.808s
user 0m3.237s
sys 0m6.614s
3
ok 10 selftests: proc: proc-uptime-001
real 0m10.577s
user 0m3.377s
sys 0m7.269s
4
ok 10 selftests: proc: proc-uptime-001
real 0m12.424s
user 0m3.215s
sys 0m7.402s
5
not ok 10 selftests: proc: proc-uptime-001 # exit=134
real 0m11.101s
user 0m3.257s
sys 0m6.883s
6
not ok 10 selftests: proc: proc-uptime-001 # exit=134
real 0m10.797s
user 0m3.199s
sys 0m6.671s
7
not ok 10 selftests: proc: proc-uptime-001 # exit=134
real 0m12.817s
user 0m3.308s
sys 0m7.177s
8
not ok 10 selftests: proc: proc-uptime-001 # exit=134
real 0m10.816s
user 0m3.201s
sys 0m6.663s
9
not ok 10 selftests: proc: proc-uptime-001 # exit=134
real 0m10.832s
user 0m3.145s
sys 0m6.721s
10
ok 10 selftests: proc: proc-uptime-001
real 0m10.664s
user 0m3.337s
sys 0m7.375s
prev parent reply other threads:[~2021-11-18 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 14:37 Re: [PATCH 5.10 000/578] 5.10.80-rc2 review Tim Lewis
2021-11-18 10:40 ` Naresh Kamboju
2021-11-18 15:37 ` Tim Lewis [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='CA+3zgmtwFQNc05why_bT1fXxPM2ShHtZ=MaB6QOmkYw81wKn6A@mail.gmail.com' \
--to=elatllat@gmail.com \
--cc=anders.roxell@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.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;
as well as URLs for NNTP newsgroup(s).