From: chrubis@suse.cz
To: Ramesh <rameshyr@linux.vnet.ibm.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] syscalls/mount0* and inotify03 tests are getting skipped from runltp
Date: Tue, 26 Mar 2013 20:47:18 +0100 [thread overview]
Message-ID: <20130326194718.GA11865@rei.suse.cz> (raw)
In-Reply-To: <5151E122.3090203@linux.vnet.ibm.com>
Hi!
> I tried to run syscalls test with ./runltp -f syscalls, it's found that
> the below tests
> are getting skipped from the run,
> -----------
> inotify03 inotify03 -D DEVICE -T DEVICE_FS_TYPE
> mount01 mount01 -D DEVICE -T DEVICE_FS_TYPE
> mount02 mount02 -D DEVICE -T DEVICE_FS_TYPE
> mount03 mount03 -D DEVICE -T DEVICE_FS_TYPE
> mount04 mount04 -D DEVICE -T DEVICE_FS_TYPE
> umount01 umount01 -D DEVICE -T DEVICE_FS_TYPE
> umount02 umount02 -D DEVICE -T DEVICE_FS_TYPE
> umount03 umount03 -D DEVICE -T DEVICE_FS_TYPE
> -----------
>
> I didn't get the value of DEVICE & DEVICE_FS_TYPE in any of conf files
> and also, as
> the tests expect a block device, I executed the tests by specifying a
> block device
> (-D /dev/sda1 -T ext4), tests passed.
>
> Also,as the DEVICE & DEVICE_FS_TYPE need to be explicitly specifed to
> all the tests,
> these tests should be commented out in ltp/runtest/syscalls which is
> used by runltp.
>
> Any comments on this issue are appreciated.
The runtest files are processed before they are executed. See -b DEVICE and
-B DEVICE_FS_TYPE runltp parameters.
The current runltp script is more of the hack than solution. I've send a
RFC email with a description of planned successor to the LTP mailing
list not that long ago (but I haven't started writing the code yet).
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Own the Future-Intel® Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest.
Compete for recognition, cash, and the chance to get your game
on Steam. $5K grand prize plus 10 genre and skill prizes.
Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2013-03-26 19:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 17:55 [LTP] syscalls/mount0* and inotify03 tests are getting skipped from runltp Ramesh
2013-03-26 19:47 ` chrubis [this message]
[not found] ` <51529266.2080906@linux.vnet.ibm.com>
2013-03-27 10:28 ` chrubis
[not found] ` <515C133C.6030803@linux.vnet.ibm.com>
2013-04-03 11:47 ` chrubis
[not found] ` <515C5D28.3050604@linux.vnet.ibm.com>
2013-04-04 11:59 ` 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=20130326194718.GA11865@rei.suse.cz \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=rameshyr@linux.vnet.ibm.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