On Tue, 2007-12-18 at 15:49 +0100, Aurélien Charbon wrote:
> I think the natural place for including these tests is the 
> testcases/network/rpc branch.
> 
> Do you want me to send a patch from the last ltp realease that includes 
> them in the right place ?

Yes. That would be great. Please pick up the latest LTP from:
http://prdownloads.sourceforge.net/ltp/ltp-full-20071130.tgz?download,

And i would also like to propose the following points:
1) You should know the way LTP-Network Tests are run. There are some
inherent variables set and other environmental settings done both at the
Client as well as the Server Side before these tests are executed. So,
your patch (new test cases addition for RPC and TRIPC) should be able to
adhere to all those norms. User should be able to execute your test
cases automatically when they run LTP-Network tests,
2) You should also properly document what your test cases are all about,
how they can be built, installed and executed and how their results
should be parsed in a Proper README file in any of the sub-directories
that your patch is going to create under ltp/testcases/network/rpc.
3) Include Copyright and GPLv2 definition at the beginning of each of
your new Test cases for License conformance in LTP,
4) Last and not the least, please respond to somebody if they find
problem(s) in executing your testcases by providing fixes, patches, etc
on the mailing-list.

Expecting a patch from you on this and much more contribution to LTP in
future. Good luck.

--Subrata


> 
> Best regards,
> Aurélien
> 
> Subrata Modak wrote:
> 
> >***********************
> >Warning: Your file, rpc-test-suite.tar.bz2, contains more than 32 files 
> >after decompression and cannot be scanned.
> >***********************
> >
> >
> >Well i am waiting for reply to the proposals that i made below. Is it
> >possible for you to submit a Patch on the lines other Network Tests in
> >general and NFS tests in Particular, that are written in LTP.
> >
> >I would also like to know more about the prospect of including the
> >attached test suite inside LTP from the community. What do you feel
> >about including the same in LTP after some tweaking ??
> >
> >--Subrata
> >
> >On Mon, 2007-12-10 at 15:11 +0530, Subrata Modak wrote:
> >  
> >
> >>On Mon, 2007-12-10 at 08:51 +0100, Aurélien Charbon wrote:
> >>    
> >>
> >>>Hi,
> >>>
> >>>A test-suite for RPC linux libraries has been developped by our NFSv4 team.
> >>>I sent a message with code as attachment to the ltp-list, because it 
> >>>would be great to see the code integrated and used in the LTP testsuite.
> >>>
> >>>Unfortunately I did not get any answer about that code.
> >>>
> >>>I have a question: does the code have to necessarily use the LTP test 
> >>>harness API to be included in the project ?
> >>>
> >>>Thanks you in advance for advice.
> >>>
> >>>Best regards,
> >>>
> >>>Aurélien
> >>>
> >>>      
> >>>
> >>I had replied to you earlier on this. May be the mail has not reached
> >>you. I will paste my Reply below to the same mail you sent earlier:
> >>
> >>Aurélien Charbon <[EMAIL PROTECTED]> wrote on 11/30/2007
> >>07:50:02 PM:
> >>    
> >>
> >>>Hi,
> >>>A test-suite for RPC linux libraries has been developped in our NFSv4
> >>>      
> >>>
> >>team.
> >>    
> >>
> >>>I sent a message with the code as attachment to the ltp-list, because
> >>>it would be great to see the code integrated and used in the LTP
> >>>testsuite.
> >>>      
> >>>
> >>Thank you. I received it long back. Yes it would be great to have any
> >>sort of Value addition to LTP. We welcome you to give us any nonexistent
> >>test cases to LTP. 
> >>
> >>    
> >>
> >>>Unfortunately I did not get any answer about that code.
> >>>      
> >>>
> >>Sorry for that.
> >>
> >>    
> >>
> >>>I have a question: does the code have to necessarily use the LTP test
> >>>harness API to be included in the project ?
> >>>      
> >>>
> >>May not be always. It depends on the type of Test Cases that we are
> >>trying to Integrate to LTP. For example, KDUMP is executed Exclusively
> >>and does not run with runltp script. So it is not a problem if it
> >>reports results in itś own format, but, the same is not with NUMA. So, i
> >>got the NUMA guy to write it in Ltp TEST HARNESS API. So, it depends
> >>upon the type of Integration. I think the Network testcases in LTP does
> >>not follow the LTP API as again Network Test Cases are run separately in
> >>most instances. Having said that, i would like to see your test cases in
> >>the form of some new subdirectory under ltp/testcases/network. There are
> >>already nfs and nfsv4 test cases existing. Please go through them and
> >>see whether the functionality they cover are also covered by your test
> >>cases, then in such a case there will be just the duplication of same
> >>functionality testing. Can you please come up with an idea to find out
> >>the exact place where we can comfortably put your test cases in LTP ??
> >>And then submit a Patch in this regard. I would be more than happy to
> >>see your test cases in LTP. I am attaching the same once again for
> >>everybody to review. Let us come up with an IDEA to include Charbonś
> >>contribution in LTP.
> >>
> >>--Subrata--
> >>
> >
> >
> >  
> >
> 
> 


-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

Reply via email to