From: Peng Haitao <penght@cn.fujitsu.com>
To: joshiplns@gmail.com
Cc: LTP List <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] Please clarify
Date: Sat, 04 Feb 2012 16:56:57 +0800 [thread overview]
Message-ID: <4F2CF2D9.4090004@cn.fujitsu.com> (raw)
In-Reply-To: <CADfK0X4BrdBUq=pQ8zjgsHPtbrXTz2w+xSvn+HP4UBtmMEfgZg@mail.gmail.com>
Josh! said the following on 2012-2-2 18:48:
> Hi folks,
>
> As I am testing 3.0 Kernel with 2012 January LTP version. I successfully tested the 3.0 Kernel. BUT from the result log TESTED result is 1279 and when I counted its 1274 . attached log with this mail.
>
> Result log :
> {
> -----------------------------------------------
> Total Tests: 1279
> Total Failures: 54
> Kernel Version: 3.0.12_nl-kzm-a9-rt29-00003-g5c963e0
> Machine Architecture: armv7l
> Hostname: 10.2.222.5
> -----------------------------------------------
> }
>
> BUT
>
> {
> [Joshi@myserver Desktop]$ cat 2012_LTP_Result | wc -l
> 1274
> }
>
> *So My query is about*:
> *1.**I am confusing about missing test cases - where is missing test cases?*
> *2*.*even though in log 1274 test cases, Why is showing as 1279 as TOTAL tested cases*.
I know the four cases: aio01, aio02, Cap_bounds and Filecaps.
aio01 and aio02 need header file /usr/include/libaio.h in libaio-devel.
Cap_bounds need header file /usr/include/sys/capability.h in libcap-devel.
Filecaps need command setcap, but ltp has a bug:(
When the above condition is not satisfied, the cases will not build and install.
When execute, the cases will return error, but not add in logfile.
for example:
initiation_status="pan(18488): execvp of 'filecapstest.sh' (tag Filecaps) failed. errno:2 No such file or directory"
> *3*.*How it will segregate the the test cases from runtest directory?*
If you run "/opt/ltp/runltp -f io", you will find aio01 and aio02 is not in the logfile.
--
Best Regards,
Peng
> *Please clarify these points*
>
> Thanks in advance
> Joshi
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
>
>
>
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2012-02-04 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 10:48 [LTP] Please clarify Josh!
2012-02-04 8:56 ` Peng Haitao [this message]
2012-02-07 7:05 ` Josh!
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=4F2CF2D9.4090004@cn.fujitsu.com \
--to=penght@cn.fujitsu.com \
--cc=joshiplns@gmail.com \
--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