From: David A. M. <dm...@re...> - 2003-05-07 01:37:26
|
Thanks to all for responding. <some snipping> > I recently fixed some of them, sendmsg01 and all the syslog tests. You > will have these changes in the May 8th release of LTP. I have been using an older version of LTP. I will look for this release. > do you have BASH? if NOT then runalltests.sh script will have to be > modified to work with buybox (if you have busybox instead), coz there > are certain things in runnalltests.sh that busy box ash does not like. We do have bash on the systems I'm using now, so this should not be an issue. > Like others responded select the testcase you want to execute and create > a custom command file and use the -f option to execute your custom list > of testcases. This looks like the best option for us to use, including only the testcases which are applicable to the system being tested, which brings me to my next question: Are the system requirements for these test cases documented? I have not been able to find these (although I may have missed it). I was looking for things like how much memory is required, how much storage is required (for file system and file transfer tests), is a network connection required, is swap space required, etc., on a per test case basis. For example: 1) I ran 'sched' tests, which create 1000 threads, but received an error. I think I just ran out of resources on this system. If I change it to create 500 threads (or up to 890 threads) there is no error. 2) I ran 'syscalls' tests, and several tests failed (recvmsg01, sendfile02, etc.) because I had no network connection. I would like to run all tests possible on a given target system, but need a way to identify which are possible. This leads to my third question: Has there been any effort to create a "tiered" test configuration? We were considering a way to select specific tests based on the system's capabilities, i.e., amount of memory, disk capacity (if present), network connection present, etc. In other words, a way to create a custom command file based on the system configuration. Does this sound like something that would be useful to others? > These might not be all that you have to do... you will have to hack > further to fit your requirements. It will be nice if you can share ur > hacks with us. </some snipping> We would certainly like to contribute any changes that we make back to the project. Thank you, d.marlin |