From: Mike Frysinger <vapier@gentoo.org>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: ltp-list@lists.sf.net
Subject: Re: [LTP] The Best Practice to Skip Syscall Tests
Date: Mon, 24 Aug 2009 04:51:12 -0400 [thread overview]
Message-ID: <200908240451.14426.vapier@gentoo.org> (raw)
In-Reply-To: <alpine.LRH.2.00.0908241040450.31587@vixen.sonytel.be>
[-- Attachment #1.1: Type: Text/Plain, Size: 1037 bytes --]
On Monday 24 August 2009 04:44:05 Geert Uytterhoeven wrote:
> On Sat, 22 Aug 2009, Mike Frysinger wrote:
> > On Saturday 22 August 2009 22:37:28 CAI Qian wrote:
> > > ENOSYS is the expected result if the kernel under test has no such
> > > implementation, so I would consider TPASS or TCONF.
> >
> > TPASS is wrong. in another thread, people seemed to be OK with TCONF.
>
> Still, the summary only shows `FAIL' or `PASS'. What is it supposed to
> show for TCONF?
i think acct01 handles this OK:
if (errno == ENOSYS) {
tst_resm(TCONF,
"BSD process accounting is not configured in this kernel.");
tst_resm(TCONF, "Test will not run.");
tst_exit();
although we could perhaps codify this nicely by adding a new
tst_missing_support() or similar function that would do this kind of thing.
first argument would be an explanatory message like "BSD process accounting is
not configured in this kernel". any suggestions for a better function name ?
-mike
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 355 bytes --]
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
[-- Attachment #3: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-08-24 8:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 11:57 [LTP] The Best Practice to Skip Syscall Tests CAI Qian
2009-08-21 16:00 ` Mike Frysinger
2009-08-21 21:17 ` Garrett Cooper
2009-08-23 2:37 ` CAI Qian
2009-08-23 3:52 ` Mike Frysinger
2009-08-24 8:44 ` Geert Uytterhoeven
2009-08-24 8:51 ` Mike Frysinger [this message]
2009-08-23 2:30 ` CAI Qian
2009-08-23 3:28 ` Garrett Cooper
2009-08-23 3:57 ` Mike Frysinger
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=200908240451.14426.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=ltp-list@lists.sf.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