Re: [LTP] the mandatory (?) nature of testscripts

[Alexey Kodanev <alexey.kodanev@oracle.com>]

Hi Jiri!
On 30.01.2015 17:18, Jiri Jaburek wrote:
> Hello all,
> I normally execute the ltp suite using runltp with -f, specifying just
> the runtest files I want to execute, possibly even writing my own ones
> and using the fact that runltp detects absolute paths in the comma-
> separated list and looks for them outside /opt/ltp.
>
> >From this viewpoint, and also looking at things like
> testscripts/syscalls.sh, this approach seems perfectly valid (there's
> at least nothing against it in the documentation, as far as I can tell).
> My impression was therefore that testscripts are just convenient
> (or legacy?) ways to run big chunks of the suite.
>
> However then I found testscripts/network.sh and all the "mandatory"
> variables it exports - not using it resulted in the ping01 test failing
> due to recent rewrite in cbab2eed06. And, as it turns out, network.sh
> is not alone.

network.sh lists network variables which are needed to run all network 
tests (stress group includes additional parameters, not yet moved them 
to network.sh from networkstress.sh). In general, it is essential to 
define remote host name, test interface names, IP addresses before 
running network tests. Not all of them run with localhost, e.g. ping01 
was modified to support various network configuration, you can now run 
it on several interfaces (probably testing various NIC drivers, make 
test traffic run over particular net-link, etc.) or running with 
localhost, for example:

$ echo 'ping601 ping01 -6' > runtest/ping_ipv6
$ RHOST_IPV6_HOST=':1' ./runltp -f ping_ipv6

> Therefore I would like to ask (since I didn't find this documented);
> is running individual tests via runltp -f something "officially"
> supported and the network tests should be altered to get their defaults
> in another way, or is runltp -f wild west and I'm on my own, with the
> only supported way to run the suite being the testscripts?

Test network configuration should be explicitly defined beforehand. You 
could set required parameters in your test environment, then use 
"runltp" as usual. I'm not sure right now if it is ok to add these 
parameters with default values to runltp, then export those variables 
inside it.

Best regards,
Alexey


------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list