All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shi Weihua <shiwh@cn.fujitsu.com>
To: Garrett Cooper <yanegomi@gmail.com>,
	Rishikesh <risrajak@linux.vnet.ibm.com>
Cc: ltp-list <ltp-list@lists.sourceforge.net>
Subject: [LTP] [BUG?] container_test.sh: should to delete check_for_unshare's source in cvs/git ?
Date: Mon, 08 Mar 2010 10:56:33 +0800	[thread overview]
Message-ID: <4B946761.8030301@cn.fujitsu.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]

Tested the latest cvs version (about Mar 1) on my x86_64 (2.6.33).
The following message occured:
--------------------------------
<<<test_start>>>
tag=Containers stime=1267527554
cmdline="container_test.sh"
contacts=""
analysis=exit
<<<test_output>>>
/opt/ltp/testcases/bin/container_test.sh: line 13: check_for_unshare: command not found
Running utsns tests.
unshare tests
test 1 (unshare)
test 2 (unshare)
......
--------------------------------

I noticed that check_for_unshare had been deleted in LTP-20091031.
In ./ChangeLog (from latest cvs version)
   ...
   2905	LTP-20091031
   ...
   3141 Removed Files:
   3142 ltp/README.ltp-devel
   3143 ltp/config.mk.in
   3144 ltp/ltp-devel.spec
   3145 ltp/testcases/kernel/containers/check_for_unshare.c
   ...
   3997 LTP-20090930

Also, i noticed check_for_unshare commentted in container_test.sh in 
release version of FEBRUARY 2010. pls check the diff between cvs version 
and release version of Feb in attached file.

Now, my question: should to delete check_for_unshare's source in cvs/git ?

[-- Attachment #2: container_test.sh.diff --]
[-- Type: text/plain, Size: 1369 bytes --]

--- ltp/testcases/kernel/containers/container_test.sh	2010-02-22 14:21:40.000000000 -0500
+++ ltp-full-20100228/testcases/kernel/containers/container_test.sh	2010-03-03 11:43:19.000000000 -0500
@@ -10,11 +10,11 @@
 # any later version.
 
 #check_utsns_enabled
-check_for_unshare
-if [ $? -eq 1 ]; then
-	echo "Unshare not supported.  Not running container tests"
-	exit 0
-fi
+#check_for_unshare
+#if [ $? -eq 1 ]; then
+#	echo "Unshare not supported.  Not running container tests"
+#	exit 0
+#fi
 check_utsns_enabled
 if [ $? -eq 0 ]; then
 	echo "Running utsns tests."
@@ -46,11 +46,22 @@ else
 	echo "ipc namespaces not enabled in kernel.  Not running ipcns tests."
 fi
 
-echo "Running pidns tests."
-runpidnstest.sh
+check_pidns_enabled
+if [ $? -eq 0 ]; then
+	echo "Running pidns tests."
+	runpidnstest.sh
+else
+	echo "Process id namespaces not enabled in kernel.  Not running pidns tests."
+fi
 
-echo "Running POSIX message queue tests."
-runmqnstest.sh
+check_mqns_enabled
+if [ $? -eq 0 ]; then
+    echo "Running POSIX message queue tests."
+    runmqnstest.sh
+else
+    echo "Posix message queues or ipc namespaces not enabled in kernel."
+    echo "Not running mqns tests."
+fi
 
 check_netns_enabled
 if [ $? -eq 0 ]; then
@@ -59,4 +70,3 @@ if [ $? -eq 0 ]; then
 else
 	echo "Network namespaces not enabled in kernel.  Not running netns tests."
 fi
-

[-- Attachment #3: Type: text/plain, Size: 345 bytes --]

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev

[-- Attachment #4: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

             reply	other threads:[~2010-03-08  2:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-08  2:56 Shi Weihua [this message]
2010-03-08 15:53 ` [LTP] [BUG?] container_test.sh: should to delete check_for_unshare's source in cvs/git ? Garrett Cooper
2010-03-08 17:17   ` Rishikesh K Rajak
2010-03-09  8:39     ` Rishikesh K Rajak

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=4B946761.8030301@cn.fujitsu.com \
    --to=shiwh@cn.fujitsu.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=risrajak@linux.vnet.ibm.com \
    --cc=yanegomi@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.