From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Joerg Vehlow <lkml@jv-coder.de>, Petr Vorel <pvorel@suse.cz>,
<linux-rt-users@vger.kernel.org>, <rt@linutronix.de>
Cc: <ltp@lists.linux.it>, Carlos Hernandez <ceh@ti.com>
Subject: Re: [LTP] LTP realtime tests
Date: Fri, 6 Dec 2019 17:50:27 +0200 [thread overview]
Message-ID: <bc04bede-48fb-68e4-2ade-6125268008a4@ti.com> (raw)
In-Reply-To: <6a7fbfdf-4fda-70bb-01d8-19fb6218170d@jv-coder.de>
CC:
On 06/12/2019 08:13, Joerg Vehlow wrote:
> Hi Petr,
>
> we are running these tests and from what I've seen the quality is very poor.
> We had to make changes to a lot of them to make them pass reliably:
> most of the tests: Missing checks of return value for pthread function and resulting deadlock
> prio-wake and prio-preempt: Bound to a single cpu core
> sched_football: Needs a sleep to run reliable (I send a mail some time ago to this mailing list
> regarding the validity of the test, which got forwarded to lkml by cyril, but no reply)
>
> Some tests do not return the correct result e.g.:
> testpi-5, testpi-6, sched_jitter, gtod_latency
>
> I haven't really looked into most of these tests.
>
> Jörg
>
> Am 05.12.2019 um 14:50 schrieb Petr Vorel:
>> Hi RT folks,
>>
>> looking into LTP realtime tests (testcases/realtime/ [1]),
>> the code certainly deserves cleanup.
>>
>> Looking at [2], it does not mention these tests at all.
>> Can anyone comment on relevance of these tests to current RT?
>> Does anyone use these tests?
>>
>> Thanks for feedback.
>>
>> Kind regards,
>> Petr
>>
>> [1] https://github.com/linux-test-project/ltp/tree/master/testcases/realtime
>> [2] https://elinux.org/Realtime_Testing_Best_Practices#Test_programs
>>
>
--
Best regards,
grygorii
prev parent reply other threads:[~2019-12-06 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 13:50 LTP realtime tests Petr Vorel
2019-12-06 6:13 ` [LTP] " Joerg Vehlow
2019-12-06 15:50 ` Grygorii Strashko [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=bc04bede-48fb-68e4-2ade-6125268008a4@ti.com \
--to=grygorii.strashko@ti.com \
--cc=ceh@ti.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=lkml@jv-coder.de \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
--cc=rt@linutronix.de \
/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).