public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: chrubis@suse.cz
To: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>
Cc: vasily.isaenko@oracle.com, ltp-list@lists.sourceforge.net
Subject: Re: [LTP] rpc-tirpc-full-test-suite
Date: Wed, 26 Feb 2014 16:08:50 +0100	[thread overview]
Message-ID: <20140226150850.GB27609@rei> (raw)
In-Reply-To: <530DF8C6.50600@oracle.com>

Hi!
> > You can skip the whole subdirectory in rpc/Makefile if tirpc is not
> > found with:
> >
> > ifeq ($(RPC_LIBS),)
> > FILTER_OUT_DIRS+=rpc-tirpc-full-test-suite
> > endif
> >
> > Assuming that the RPC_LIBS behaves the same way as NUMA_LIBS for
> > example.
> >
> > And please shorten the directory names when you are at it,
> > rpc-tirpc-full-test-suite is far to long and tirpc or similar would do
> > the same job.
> 
> Sorry, did you mean to rename rpc-tirpc-full-test-suite to tirpc or 
> similar?

Yes, I'm not a friend of overly descriptive names. So either tirpc or
tirpc-test-suite or anything short enough and descriptive.

> >> Make corresponding changes in current execution/building infrastructure
> >> under rpc-tirpc-full-test-suite. Maybe someone will need it. And I don't
> >> feel that I have a right to remove all these shell scripts and etc.
> >
> > I would personaly remove the current execution/building infrastructure
> > and focus on the LTP integration. Managing two parallel systems is much
> > more work and unless somebody will use the current system it will get
> > broken sooner or later.
> 
> Ok. But maybe move this stuff into a subdirectory under 
> rpc-tirpc-full-test-suite? Just in case...

I would not bother, it's contained in about 10 released LTP tarballs
that are all archived in sf.net download area and it's in a git history
as well and the original tarball is stil reachable at:
http://nfsv4.bullopensource.org/doc/rpc_testsuite.php

Let's concentrate on making it run flawlessly in default LTP run.

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  parent reply	other threads:[~2014-02-26 15:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-26  9:07 [LTP] rpc-tirpc-full-test-suite Stanislav Kholmanskikh
2013-12-26  9:07 ` [LTP] [PATCH 1/5] rpc-tirpc-full-test-suite: do not use tst_exit Stanislav Kholmanskikh
2013-12-26  9:07 ` [LTP] [PATCH 2/5] rpc-tirpc-full-test-suite: enabled build of the rpc test cases Stanislav Kholmanskikh
2014-02-11 15:42   ` chrubis
2013-12-26  9:07 ` [LTP] [PATCH 3/5] rpc-tirpc-full-test-suite: fixed the cmdline in runtest Stanislav Kholmanskikh
2014-02-11 15:46   ` chrubis
2013-12-26  9:07 ` [LTP] [PATCH 4/5] rpc-tirpc-full-test-suite: pass exit value to the wrapper Stanislav Kholmanskikh
2014-02-11 15:54   ` chrubis
2013-12-26  9:07 ` [LTP] [PATCH 5/5] rpc_stdcall_basic_lib: fixed IS_EX match Stanislav Kholmanskikh
2014-02-11 15:10 ` [LTP] rpc-tirpc-full-test-suite chrubis
     [not found]   ` <530C7004.3060102@oracle.com>
2014-02-26 13:47     ` chrubis
     [not found]       ` <530DF8C6.50600@oracle.com>
2014-02-26 15:08         ` chrubis [this message]
     [not found]           ` <5317454D.5010505@oracle.com>
2014-03-11 14:02             ` chrubis
     [not found]               ` <531F1FEE.1060001@oracle.com>
2014-03-11 15:08                 ` chrubis

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=20140226150850.GB27609@rei \
    --to=chrubis@suse.cz \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=stanislav.kholmanskikh@oracle.com \
    --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