From: Cyril Hrubis <chrubis@suse.cz>
To: Xinkuan Yan <lucky33newman@gmail.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] About those realtime tests.
Date: Wed, 7 Dec 2022 17:15:36 +0100 [thread overview]
Message-ID: <Y5C8KLaOi2U00Xwu@yuki> (raw)
In-Reply-To: <CAFQkDybMFX16dSaW+eZ0rC7TAwD5O7RnCkSuTS-ka9zZwKjC6Q@mail.gmail.com>
Hi!
> Green hand here to ask a question about thost realtime tests, I mean, tests
> under this folder:
>
> /opt/ltp/testcases/realtime/func
>
> I surely knew that those tests could be started with 'run_auto.sh', and
> most of them provide reports with PASS or FAIL.
>
> The question for me is that is it possible to use the script file 'runltp'
> to start those tests?
>
> I have read the doc ltp-run-files.txt but I did not quite get to it.
>
> Any guidance is appreciated!
I do not think that writing realtime tests runtest file is an easy task.
First of all there is a profile/default that has harcoded constants that
worked once for someone running the testsuite, but that is supposed to
be tweaked. There are no good values for these constants, these have to
be tailored to a machine and usecase. Moreover some of these tests does
not even interpret the results and just return measurements, these can't
be integrated into a runtest file at all.
Secondly runtest files are suppose to have one test per entry, so you
would have to pick up how binaries are executed in run_auto.sh files in
the func/*/ directories and use the default values from the default
profile in the cases. And that only works for the subset of tests that
does report pass/fail status in the exit value.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2022-12-07 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 7:52 [LTP] About those realtime tests Xinkuan Yan
2022-12-07 16:15 ` Cyril Hrubis [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=Y5C8KLaOi2U00Xwu@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=lucky33newman@gmail.com \
/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