From: Richard Palethorpe <rpalethorpe@suse.de>
To: Joerg Vehlow <lkml@jv-coder.de>
Cc: LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [REGRESSION] lkft ltp for 6763a36
Date: Tue, 21 Jun 2022 09:35:55 +0100 [thread overview]
Message-ID: <871qvi5r97.fsf@suse.de> (raw)
In-Reply-To: <60876a29-d589-1de9-b4fd-a9000b8e7d68@jv-coder.de>
Hello,
Joerg Vehlow <lkml@jv-coder.de> writes:
> Hi Jan,
>
> Am 6/21/2022 um 9:22 AM schrieb Jan Stancek:
>> On Tue, Jun 21, 2022 at 9:15 AM Joerg Vehlow <lkml@jv-coder.de> wrote:
>>>
>>> Hi,
>>>
>>> Am 6/17/2022 um 3:17 AM schrieb lkft@linaro.org:
>>>> * qemu_i386, ltp-fs-tests
>>>> - read_all_proc
>>> I've seen this test fail a lot, has anyone ever tried to analyze it? I
>>> was unable to reproduce the problem when running the test in isolation.
>>
>> I see it hit timeouts too (read_all_sys as well). I think it needs
>> runtime restored to 5minutes as well, atm. it has 30s.
> Didn't think about that, but at least for the failures I've seen, this
> is not the reason. The message printed by the test is "Test timeout 5
> minutes exceeded."
>
> Joerg
The main issue with read_all is that it also acts as a stress
test. Reading some files in proc and sys is very resource intensive
(e.g. due to lock contention) and varies depending on what state the
system is in. On some systems this test will take a long time. Also
there are some files which have to be filtered from the test. This
varies by system as well.
--
Thank you,
Richard.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-06-21 8:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 1:17 [LTP] [REGRESSION] lkft ltp for 6763a36 lkft
2022-06-21 7:15 ` Joerg Vehlow
2022-06-21 7:22 ` Jan Stancek
2022-06-21 7:56 ` Joerg Vehlow
2022-06-21 8:35 ` Richard Palethorpe [this message]
2022-06-21 9:45 ` Li Wang
2022-06-21 11:38 ` Richard Palethorpe
2022-06-21 12:51 ` Joerg Vehlow
2022-06-23 10:51 ` Richard Palethorpe
2022-06-22 7:39 ` Martin Doucha
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=871qvi5r97.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=lkml@jv-coder.de \
--cc=ltp@lists.linux.it \
/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