From: Hushan Jia <hjia@redhat.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] [PATCH] network: Fix ip_tests error 2
Date: Fri, 11 Sep 2009 09:58:13 +0800 [thread overview]
Message-ID: <4AA9AEB5.3020905@redhat.com> (raw)
Hello,
Repost the ip tests patch:
1. Test #4:
ip tools now print nud state as follows:
REACHABLE, STALE, FAILED, etc.
2. Test #3, #4, #5:
If delete entry succefully, grep will return 1,
indicating test PASS, so return code RC should be set to 0.
Thanks & Regards,
Hushan
---
network: Fix iproute test case error 2
Signed-off-by: Hushan Jia <hjia@redhat.com>
--- ltp/testcases/network/iproute/ip_tests.sh.orig 2009-09-09 18:31:31.000000000 +0800
+++ ltp/testcases/network/iproute/ip_tests.sh 2009-09-09 18:32:43.000000000 +0800
@@ -310,7 +310,9 @@ test03()
tst_res TFAIL $LTPTMP/tst_ip.err \
"Test #3: ip addr del command failed. Reason: "
return $(($RC+1))
- fi
+ else
+ RC=0
+ fi
tst_resm TPASS \
"Test #3: ip addr command tests successful"
@@ -354,7 +356,7 @@ test04()
"Test #4: ip neigh show - shows all neighbour entries in arp tables."
cat > $LTPTMP/tst_ip.exp <<-EOF
- 127.0.0.1 dev lo lladdr 00:00:00:00:00:00 nud reachable
+ 127.0.0.1 dev lo lladdr 00:00:00:00:00:00 REACHABLE
EOF
ip neigh show 127.0.0.1 | head -n1 >$LTPTMP/tst_ip.out 2>&1 || RC=$?
@@ -384,12 +386,14 @@ test04()
"Test #4: ip neigh del command failed return = $RC. Reason: "
return $RC
else
- ip neigh show | grep 127.0.0.1 grep -v "nud failed$" >$LTPTMP/tst_ip.err 2>&1 || RC=$?
+ ip neigh show | grep 127.0.0.1 | grep -v " FAILED$" >$LTPTMP/tst_ip.err 2>&1 || RC=$?
if [ $RC -eq 0 ]
then
tst_res TFAIL $LTPTMP/tst_ip.err \
"Test #4: 127.0.0.1 still listed in arp. ip cmd Error Message:"
return $(($RC+1))
+ else
+ RC=0
fi
fi
@@ -482,6 +486,8 @@ test05()
tst_res TFAIL $LTPTMP/tst_ip.err \
"Test #5: route not deleted. ip route show:"
return $(($RC+1))
+ else
+ RC=0
fi
fi
@@ -570,6 +576,8 @@ test06()
tst_res TFAIL $LTPTMP/tst_ip.err \
"Test #6: 66:66:00:00:00:66 is not deleted. Details:"
return $(($RC+1))
+ else
+ RC=0
fi
fi
------------------------------------------------------------------------------
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
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2009-09-11 2:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 1:58 Hushan Jia [this message]
2009-09-13 13:17 ` [LTP] [PATCH] network: Fix ip_tests error 2 Subrata Modak
-- strict thread matches above, loose matches on Subject: below --
2009-09-07 11:20 [LTP] [PATCH] network: Fix ip_tests error Hushan Jia
2009-09-07 11:38 ` Subrata Modak
2009-09-08 1:22 ` [LTP] [PATCH] network: Fix ip_tests error 2 Hushan Jia
2009-09-09 6:49 ` Subrata Modak
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=4AA9AEB5.3020905@redhat.com \
--to=hjia@redhat.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 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.