Just wanted to convey that, please, note the following points when you are writing a Test case for LTP: 1) Make sure that the test case(s) run(s) under all kernels (both 32 bit or 64 bit as well as kernel trees like 2.6.18, 2.6.19.....). If it is not supported by that kernel version, then compile appropriate message(s) during test case compilation. The basic idea is that the test case should be able to determine whether it is supported on the kernel it is being built. If yes, go ahead with that test else display appropriate message(s) and should not crash un-wantedly. 2) Make sure that the test case(s) run(s) under all architectures too. You need to use appropriate logic to check architecture during compilation and then to go ahead (or not) with the tests.
All these and above are necessary to maintain generality and backward compatibility which we envisage to follow in any future new test cases in LTP. Thanks-- Subrata On Mon, 2007-11-12 at 15:22 +0530, Subrata Modak1 wrote: > [EMAIL PROTECTED] wrote on 11/12/2007 03:03:42 PM: > > > Hi, > > > > I'm interested in writing testcases for fadvise64 > > and posix_fadvise. I'd like to get some hints before > > starting work. > > Thanks. You will get all hints that you require for > writing new test cases. > > > > > Test cases for fadvise64 may should be put at > > ltp/testcases/kernel/syscalls/fadvise64. > > You are correct. You have to put the corresponding test cases > source code and Makefile in this directory. By the way, how many > test cases are you going to write for this syscall ? > > > > > How about posix_fadvise? > > At first sight, I think it should be put at > > somewhere in ltp/testcases/open_posix_testsuite/. > > However, it seems that open_posix_testsuite/ comes from > > posixtest project. So should I contact with posixtest project? > > Comparing LTP, posixtest is not so active these days. So > > I wonder where I should submit a testcase for posix_fadvise. > > You should nevertheless go ahead and write it in the posixtest > format and submit the same to posixtest and cc to LTP-list. We will > see whether there is any response from posixtest. However we will > include it inside LTPś OPEN_POSIX_TESTSUITE and will inform them > about the code changes in POSIXTEST available in LTP, when they > do their next release. Even if they are not active, we will do the > backup on their part. > > > > > Regards, > > Masatake YAMATO > > Also please let me know if you are interested to write other test cases > also (may be for some more missing system calls and so). > > Thanks-- > Subrata > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > Ltp-list mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/ltp-list > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Ltp-list mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ltp-list ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
