public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Alexey Kodanev <alexey.kodanev@oracle.com>
To: ltp@lists.linux.it
Subject: [LTP] Invoking networking tests
Date: Thu, 8 Dec 2016 14:26:08 +0300	[thread overview]
Message-ID: <58494350.80404@oracle.com> (raw)
In-Reply-To: <20161207141855.lvyrqs4cxhy4wr2c@dell5510>

Hi Petr,

On 12/07/2016 05:18 PM, Petr Vorel wrote:
> Hi Alexey,
>
> we're going to run LTP networking tests to against openSUSE and SUSE. Is there anything
> you'd like to change on invoking these tests? Anything deprecated?

You can invoke network test as other LTP tests, just make sure you 
provided all
the necessary environment variables, all of them have default values, so 
youneed to
make sure they were set appropriately according to your environment.

Please also see the recent patch:
5f8ca6c ("network: test_net.sh: allow to run network tests on a single 
machine")

And any improvements are always welcome.

> I see that scripts are run by ltp-pan (via. testscripts/network.sh wrapper), which is I
> suppose standard way how to run any test in LTP (as it is in runltp and half of
> testscripts/*.sh scripts).
> How about testcases/lib/test_net.sh and testcases/lib/test.sh scripts? Not deprecated?

Not deprecated, i.e. if you encounter that a shell test not using either 
of these two,
it's quite outdated and needs to be converted to the newer library.

> BTW: what is the purpose of testscripts/*.sh scripts, why it isn't everything integrated
> into runltp?

Just a wrapper script for ltp-pan, provides convenient options to run 
network tests.
Some time ago network.sh used to have more functionality, like default 
values for
network environment variables, but now they all have moved to 
test_net.sh so we
don't depend on this script anymore.

Best regards,
Alexey


  reply	other threads:[~2016-12-08 11:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07 14:18 [LTP] Invoking networking tests Petr Vorel
2016-12-08 11:26 ` Alexey Kodanev [this message]
2016-12-08 17:32   ` Petr Vorel
2016-12-12 11:52     ` Alexey Kodanev
2016-12-12 13:52       ` Cyril Hrubis
2016-12-12 13:56         ` Cyril Hrubis
2016-12-12 14:20 ` Cyril Hrubis

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=58494350.80404@oracle.com \
    --to=alexey.kodanev@oracle.com \
    --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