From: "Mitani" <mitani@ryobi.co.jp>
To: ltp-list@lists.sourceforge.net
Cc: "當座 健市" <toza@ryobi.co.jp>
Subject: [LTP] [PATCH] fix "sched_getparam/6-1" and "sched_getscheduler/7-1" tests
Date: Wed, 8 Dec 2010 15:56:42 +0900 [thread overview]
Message-ID: <000001cb96a5$12026c30$36074490$@co.jp> (raw)
[-- Attachment #1: Type: text/plain, Size: 2354 bytes --]
Hi,
Following POSIX testsets failed:
------------
conformance/interfaces/sched_getparam/6-1: execution: FAILED: Output:
Testing with user 'bin' (euid: 1)(uid: 1)
The function sched_getparam has successed.
------------
------------
conformance/interfaces/sched_getscheduler/7-1: execution: FAILED: Output:
Testing with user 'bin' (uid: 1)
The function sched_getscheduler has successed.
------------
The environments are as follows:
- RHEL4.8 --- (x86, x86_64, ia64)
- kernel --- kernel-2.6.9-89.EL
- glibc --- glibc-2.3.4-2.43
- RHEL5.5 --- (x86, x86_64, ia64)
- kernel --- kernel-2.6.18-194.el5
- glibc --- glibc-2.5-49
They are permission tests.
The comment of "sched_getparam/6-1" testset source is as follows:
------------
* On Linux, e.g, the kernel makes no check on user permission to call this
* API. So basically we don't know on what condition a system should return
* EPERM. It is implementation defined.
------------
Therefore I revised their results to "UNRESOLVED" by judging linux
environment.
Signed-off-by: Tomonori Mitani <mitani@ryobi.co.jp>
============
---
a/testcases/open_posix_testsuite/conformance/interfaces/sched_getparam/6-1.c
2010-12-08 15:39:45.000000000 +0900
+++
b/testcases/open_posix_testsuite/conformance/interfaces/sched_getparam/6-1.c
2010-12-08 13:48:51.000000000 +0900
@@ -65,6 +65,11 @@
struct sched_param param;
int result = -1;
+#ifdef __linux__
+ printf("We don't know on what condition a system should return
EPERM.\n");
+ return PTS_UNRESOLVED;
+#endif
+
/* We assume process Number 1 is created by root */
/* and can only be accessed by root */
/* This test should be run under standard user permissions */
============
============
---
a/testcases/open_posix_testsuite/conformance/interfaces/sched_getscheduler/7
-1.c 2010-11-12 02:19:16.000000000 +0900
+++
b/testcases/open_posix_testsuite/conformance/interfaces/sched_getscheduler/7
-1.c 2010-12-08 15:42:23.000000000 +0900
@@ -55,6 +55,11 @@
int result = -1;
+#ifdef __linux__
+ printf("We don't know on what condition a system should return
EPERM.\n");
+ return PTS_UNRESOLVED;
+#endif
+
/* We assume process Number 1 is created by root */
/* and can only be accessed by root */
/* This test should be run under standard user permissions */
============
Regards--
-Tomonori Mitani
[-- Attachment #2: 7-1.patch --]
[-- Type: application/octet-stream, Size: 588 bytes --]
--- a/testcases/open_posix_testsuite/conformance/interfaces/sched_getscheduler/7-1.c 2010-11-12 02:19:16.000000000 +0900
+++ b/testcases/open_posix_testsuite/conformance/interfaces/sched_getscheduler/7-1.c 2010-12-08 15:42:23.000000000 +0900
@@ -55,6 +55,11 @@
int result = -1;
+#ifdef __linux__
+ printf("We don't know on what condition a system should return EPERM.\n");
+ return PTS_UNRESOLVED;
+#endif
+
/* We assume process Number 1 is created by root */
/* and can only be accessed by root */
/* This test should be run under standard user permissions */
[-- Attachment #3: 6-1.patch --]
[-- Type: application/octet-stream, Size: 613 bytes --]
--- a/testcases/open_posix_testsuite/conformance/interfaces/sched_getparam/6-1.c 2010-12-08 15:39:45.000000000 +0900
+++ b/testcases/open_posix_testsuite/conformance/interfaces/sched_getparam/6-1.c 2010-12-08 13:48:51.000000000 +0900
@@ -65,6 +65,11 @@
struct sched_param param;
int result = -1;
+#ifdef __linux__
+ printf("We don't know on what condition a system should return EPERM.\n");
+ return PTS_UNRESOLVED;
+#endif
+
/* We assume process Number 1 is created by root */
/* and can only be accessed by root */
/* This test should be run under standard user permissions */
[-- Attachment #4: Type: text/plain, Size: 450 bytes --]
------------------------------------------------------------------------------
What happens now with your Lotus Notes apps - do you make another costly
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
[-- Attachment #5: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2010-12-08 6:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 6:56 Mitani [this message]
2011-01-24 9:58 ` [LTP] [PATCH] fix "sched_getparam/6-1" and "sched_getscheduler/7-1" tests Bian Naimeng
2011-01-24 10:56 ` Garrett Cooper
2011-01-25 3:11 ` Bian Naimeng
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='000001cb96a5$12026c30$36074490$@co.jp' \
--to=mitani@ryobi.co.jp \
--cc=ltp-list@lists.sourceforge.net \
--cc=toza@ryobi.co.jp \
/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