Hi Cyril,

here’s a patch that adds the block device (and block device file system type) 
options to the runltplite script. Assumption is that runltp and runltplite will 
(continue to) reside in the same directory.

Thanks & cheerio, Harry.

Attachment: runltplite-block-device.patch
Description: Binary data


On Feb 19, 2014, at 6:41 AM, [email protected] wrote:

> Hi!
>> using runltplite, access06 is reported as broken because DEVICE and
>> DEVICE_FS_TYPE aren't set.
>> 
>> Unlike runltp there's no command line option or fallback mechanism
>> implemented in the runltplite script. Should access06 be taken out of
>> runltplite!?
> 
> There is increasing number testcases that needs a device for EROFS error
> tests.
> 
> Ideally runltplite.sh should prepare and export the device just as
> runltp does, this should fix the testruns for now. Do you care to send a
> patch? :)
> 
> Better solution would be to skip the EROFS test if device wasn't set and
> print a warning but this would require changes in the LTP test library
> (I have this on my longterm TODO).
> 
> -- 
> Cyril Hrubis
> [email protected]

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

Reply via email to