public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: "Mitani" <mitani@ryobi.co.jp>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] ”Containers” test was "TFAIL" but "PASS" is in log results
Date: Fri, 16 Jul 2010 13:19:28 +0900	[thread overview]
Message-ID: <000001cb249e$14ed7490$3ec85db0$@co.jp> (raw)

Hi,

With RHEL5.4/5.5 systems, I noticed that "Containers" test failed but 
"Containers" is PASS in log results:

---<log results file>-------------
...
hangup01                       PASS       0    
Containers                     PASS       0    
BindMounts                     PASS       0    
...
----------------

---<detail in redirected file>-------------
...
check_netns_enabled    1  TFAIL  :  unshare syscall smoke test failed:
errno=EINVAL(22): Invalid argument
Network namespaces not enabled in kernel.  Not running netns tests.
...
----------------

The source which returned with "Invalid argument" is
"check_netns_enabled.c":

---<check_netns_enabled.c>-------------
main()
{
        /* Checking if the kernel supports unshare with netns capabilities.
*/
        if (syscall(__NR_unshare, CLONE_NEWNET | CLONE_NEWNS) < 0) {
                tst_resm (TFAIL | TERRNO, "unshare syscall smoke test
failed");
        }
        tst_exit();
}
----------------

In RHEL5.4/5.5 systems, unshare() does not support the argument 
"CLONE_NEWNET".
But I feel strange that log results is "PASS" in spite of "TFAIL" exit. 

"container_test.sh" which calls "check_netns_enabled.c" is as follows:
---<container_test.sh>-------------
...
check_netns_enabled
if [ $? -eq 0 ]; then
        echo "Running netns tests."
        runnetnstest.sh
else
        echo "Network namespaces not enabled in kernel.  Not running netns
tests."
fi
...
----------------

According to above source, "check_netns_enabled.c" is only the judgement 
whether "runnetnstest.sh" test can be called or not.
So, I think that "TFAIL" is not suitable for the test impossibility 
message.
"TCONF" is more suitable for the message than "TFAIL", I think.
But, if "TCONF" is used instead of "TFAIL", "tst_exit" returns with 0.
And the test shell "runnetnstest.sh" is called against intention.


I thought up two ways of solutions.
(1) Insert "exit(1)" just after "tst_resm()" of "check_netns_enabled.c"
(2) Replace "TFAIL" with "TWARN", instead of "TCONF".

But above solutions are both irregular measures, I think.

If there are other good measures, please give me advice.


In the following, I nominate a temporary patch for an example:

Signed-off-by: Tomonori Mitani <mitani@ryobi.co.jp>

===(1)=========
--- a/testcases/kernel/containers/netns/check_netns_enabled.c	2010-07-12
02:01:45.000000000 +0900
+++ b/testcases/kernel/containers/netns/check_netns_enabled.c	2010-07-16
11:58:14.000000000 +0900
@@ -43,7 +43,8 @@
 {
 	/* Checking if the kernel supports unshare with netns capabilities.
*/
         if (syscall(__NR_unshare, CLONE_NEWNET | CLONE_NEWNS) < 0) {
-		tst_resm (TFAIL | TERRNO, "unshare syscall smoke test
failed");
+		tst_resm (TCONF | TERRNO, "unshare syscall smoke test
failed");
+		exit (1);
 	}
 	tst_exit();
 }
============

===(2)=========
--- a/testcases/kernel/containers/netns/check_netns_enabled.c	2010-07-12
02:01:45.000000000 +0900
+++ b/testcases/kernel/containers/netns/check_netns_enabled.c	2010-07-16
11:56:47.000000000 +0900
@@ -43,7 +43,7 @@
 {
 	/* Checking if the kernel supports unshare with netns capabilities.
*/
         if (syscall(__NR_unshare, CLONE_NEWNET | CLONE_NEWNS) < 0) {
-		tst_resm (TFAIL | TERRNO, "unshare syscall smoke test
failed");
+		tst_resm (TWARN | TERRNO, "unshare syscall smoke test
failed");
 	}
 	tst_exit();
 }
============



Regards--

-Tomonori Mitani



------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

             reply	other threads:[~2010-07-16  4:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-16  4:19 Mitani [this message]
2010-07-16 22:50 ` [LTP] ”Containers” test was "TFAIL" but "PASS" is in log results Garrett Cooper
2010-07-16 22:50   ` Garrett Cooper
2010-08-02  4:36     ` Mitani
2010-08-02  6:31       ` Garrett Cooper

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='000001cb249e$14ed7490$3ec85db0$@co.jp' \
    --to=mitani@ryobi.co.jp \
    --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