All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Kodanev <alexey.kodanev@oracle.com>
To: ltp@lists.linux.it
Subject: [LTP] Invoking networking tests
Date: Mon, 12 Dec 2016 14:52:20 +0300	[thread overview]
Message-ID: <584E8F74.80308@oracle.com> (raw)
In-Reply-To: <20161208173228.jixqv2xd6jqptz5i@dell5510>

Hi Petr,

On 12/08/2016 08:32 PM, Petr Vorel wrote:
> Hi Alexey,
>
> thanks for info!
>
>> Please also see the recent patch:
>> 5f8ca6c ("network: test_net.sh: allow to run network tests on a single
>> machine")
> Noticed, I was waiting for pushing it to master :-). Looks interesting, I'll give it a try.
>
> Can it be "dangerous" to run tests "natively", i.e. without ltp-pan? It'd be run by
> automation (no cancel ctrl+c), so cleanup children is unlike.

I think it depends on automation and how far it controls started process.

Besides, converted to latest LTP API tests much safer in terms of per 
test lockups because
they have a test timeout there. As far as I know there is no such 
feature in new shell library
yet (tst_test.sh). It seems that it would be a good thing to have a 
timeout option in tst_rod() too.

Thanks,
Alexey

> Or is it also for cleanup
> when some test misbehave and it's being killed by kernel?
>
>
> Kind regards,
> Petr


  reply	other threads:[~2016-12-12 11:52 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
2016-12-08 17:32   ` Petr Vorel
2016-12-12 11:52     ` Alexey Kodanev [this message]
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=584E8F74.80308@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.