Hi, Thank you for the answer. I found that those testcases are working fine with additional arguments "-b DEVICE" and "-B DEVICE_FS_TYPE" passed to runltp.
And please review my patch named "[PATCH v2] acct01: add a check routine for acct implementation" I just submitted acct01 patch once again with a simple typo fix in the commit message. I have verified it on top of the very recent commit as well. Honggyu Kim -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Wednesday, November 06, 2013 12:47 AM To: Honggyu Kim Subject: Re: a question regarding runtest modification with arguments Hi! > I'm just wondering why acct01 is not executed after the following > modification is done in runtest/syscalls. > > -acct01 acct01 > +acct01 acct01 -D DEVICE -T DEVICE_FS_TYPE Most likely your kernel has no support for loop devices and no real block device was passed to the runltp script for testing. In that case all tests that require loop device are skipped. And you could have send this mail to the LTP mailing list as well. -- Cyril Hrubis [email protected] -----Original Message----- From: Honggyu Kim [mailto:[email protected]] Sent: Tuesday, November 05, 2013 11:31 AM To: [email protected] Subject: a question regarding runtest modification with arguments Hi, I'm just wondering why acct01 is not executed after the following modification is done in runtest/syscalls. -acct01 acct01 +acct01 acct01 -D DEVICE -T DEVICE_FS_TYPE I have tested this on an ARM machine but I was not able to find the test information in the result. I also found that chmod06 has not been executed until now. chmod* in runtest/syscalls were written as follows: chmod05 chmod05 chmod06 chmod06 -D DEVICE -T DEVICE_FS_TYPE chmod07 chmod07 The strange thing is that chmod05 and chmod07 are executed and the test information is included in the result, but chmod06 is not executed at all. I observed the output file as well, but no running log was found for chmod06. I think the problems on chmod06 and modified acct01 in the runtest are the same. Please let me know if the problem comes from only my machine. The patch that I submitted just before was not related to this issue. Regards, Honggyu Kim ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
