From: chrubis@suse.cz
To: Alexey Kodanev <alexey.kodanev@oracle.com>
Cc: vasily.isaenko@oracle.com, ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH v2] lib/test_net.sh: add network help script
Date: Wed, 2 Apr 2014 18:19:04 +0200 [thread overview]
Message-ID: <20140402161904.GA30505@rei.Home> (raw)
In-Reply-To: <533C2D8A.4080502@oracle.com>
Hi!
> >> +[ -z "$TST_LIB_LOADED" ] && . test.sh
> >> +
> >> +# Run command on remote host.
> >> +# Options:
> >> +# -b run in background
> >> +# -s safe option, if something goes wrong, will exit with TBROK
> >> +# -c specify command to run
> >> +
> >> +tst_rhost_run()
> >> +{
> >> + # this is needed to run tools/apicmds on remote host
> >> + local pre_cmd="TCID=$TCID TST_COUNT=1 TST_TOTAL=1"
> > Hmm, if I get it right, this is here in order to make possible to run
> > the tst_get_unused_port apicmd command.
> >
> > I don't like that much that we have to set the TST_COUNT and TST_TOTAL
> > too. Maybe we should relax the rules in ltpapicmd.c, given that
> > TST_TOTAL is not used for anything in the lib/ directory and the
> > tst_count is used only used only in the tst_print().
> Yes, you are right, I did so because of apicmds.
> What about if we remove the check completely? We won't use tst_res*,
> tst_brk*... in new tests.
For now I've added an exception for the tst_get_unused_port the same way
we do it for tst_kvercmp. See latest git commit.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2014-04-02 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 7:01 [LTP] [PATCH v2] lib/test_net.sh: add network help script Alexey Kodanev
2014-04-02 14:53 ` chrubis
[not found] ` <533C2D8A.4080502@oracle.com>
2014-04-02 16:19 ` chrubis [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=20140402161904.GA30505@rei.Home \
--to=chrubis@suse.cz \
--cc=alexey.kodanev@oracle.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=vasily.isaenko@oracle.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