From: chrubis@suse.cz
To: Harry Weppner <harry.weppner@gmx.net>
Cc: "ltp-list@lists.sourceforge.net" <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] runltplite access06 test relies on DEVICE and DEVICE_FS_TYPE
Date: Wed, 19 Feb 2014 15:41:12 +0100 [thread overview]
Message-ID: <20140219144112.GC2138@rei> (raw)
In-Reply-To: <37DEC8B3-1B3C-4FD3-99F8-3E5436311195@gmx.net>
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
chrubis@suse.cz
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-02-19 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 1:19 [LTP] runltplite access06 test relies on DEVICE and DEVICE_FS_TYPE Harry Weppner
2014-02-19 14:41 ` chrubis [this message]
[not found] ` <4682076F-14CA-486F-9DFD-6E001FE036F7@gmx.net>
2014-03-13 15:16 ` 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=20140219144112.GC2138@rei \
--to=chrubis@suse.cz \
--cc=harry.weppner@gmx.net \
--cc=ltp-list@lists.sourceforge.net \
/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