[LTP] LTP] [PATCH ]: network stress interfaces part of the LTP stress fails

* [LTP] LTP] [PATCH ]: network stress interfaces part of the LTP stress fails
@ 2013-02-01 14:04 Bhushan Kumar
  2013-02-12 14:41 ` chrubis
  0 siblings, 1 reply; 4+ messages in thread
From: Bhushan Kumar @ 2013-02-01 14:04 UTC (permalink / raw)
  To: ltp-list


[-- Attachment #1.1: Type: text/plain, Size: 5213 bytes --]

Hi All ,

 

Description of problem:

 

I am getting error while running   if4-mtu-change and if6-updown  network stress interfaces test case  from LTP version  20120903 (ltp-full-20120903.tar) i.e.  on Linux 3.2 kernel. Below are the outputs for error.

 

 

The Network stress interfaces part of the LTP stress fails.

 

network_stress.interface:if4-mtu-change                 FAIL       2    

network_stress.interface:if6-updown                     FAIL       2  


 

Below are the cause for failing above mentioned testcase:

 

if4-mtu-change01    0  TINFO  :  Verify the IPv4 connectivity is not broken when ifconfig command changes MTU 128 times every 5 seconds

if4-mtu-change01    1  TFAIL  :  eth1 is broken.

if4-mtu-change02    0  TINFO  :  Verify the IPv4 connectivity is not broken when ip command changes MTU 128 times every 5 seconds

if4-mtu-change02    2  TBROK  :  Test Link 0 is somthing wrong.

 

if6-updown    1  TBROK  :  Link-local address is not found at eth1 on the remote host

 

Suggested Code changes:

 

To  resolve above mentioned  error  by making  changes in  ltp-full-20120903/testcases/network/stress/interface/if4-mtu-change  and  ltp-full-20120903/testcases/network/stress/interface/if6-updown b/ltp-full-20120903/testcases/network/stress/interface/if6-updown  file. Below are the code changes:

 

 

diff -Nurp a/ltp-full-20120903/testcases/network/stress/interface/if4-mtu-change b/ltp-full-20120903/testcases/network/stress/interface/if4-mtu-change

--- a/ltp-full-20120903/testcases/network/stress/interface/if4-mtu-change       2013-01-09 02:07:21.000000000 -0700

+++ b/ltp-full-20120903/testcases/network/stress/interface/if4-mtu-change       2013-02-01 05:09:51.000000000 -0700

@@ -190,6 +190,7 @@ test_body()

 

     # Check the connctivity

     check_icmpv4_connectivity $lhost_ifname $rhost_ipv4addr

+    sleep 5

     if [ $? -ne 0 ]; then

        tst_resm TBROK "Test Link $LINK_NUM is somthing wrong."

        return 1

@@ -237,6 +238,7 @@ test_body()

 

     # Check the connectivity again

     check_icmpv4_connectivity $lhost_ifname $rhost_ipv4addr

+    sleep 5

     if [ $? -ne 0 ]; then

        tst_resm TFAIL "$lhost_ifname is broken."

        return 1

diff -Nurp a/ltp-full-20120903/testcases/network/stress/interface/if6-updown b/ltp-full-20120903/testcases/network/stress/interface/if6-updown

--- a/ltp-full-20120903/testcases/network/stress/interface/if6-updown   2013-01-09 02:07:21.000000000 -0700

+++ b/ltp-full-20120903/testcases/network/stress/interface/if6-updown   2013-02-01 05:12:40.000000000 -0700

@@ -93,7 +93,7 @@ do_setup()

     # Initialize the interfaces

     initialize_if lhost ${LINK_NUM}

     initialize_if rhost ${LINK_NUM}

-

+    sleep 5

     # Get the Interface name of local host

     lhost_ifname=`get_ifname lhost ${LINK_NUM}`

     if [ $? -ne 0 ]; then

 

After the mentioned changes I got output 

 

<<<test_output>>>

/opt/ltp/testcases/bin/bg_tcp_traffic: line 269: $2: unbound variable

if4-mtu-change01    0  TINFO  :  Verify the IPv4 connectivity is not broken when ifconfig command changes MTU 128 times every 5 seconds

/opt/ltp/testcases/bin/bg_tcp_traffic: line 269: $2: unbound variable

if4-mtu-change01    1  TPASS  :  Test is finished correctly.

if4-mtu-change02    0  TINFO  :  Verify the IPv4 connectivity is not broken when ip command changes MTU 128 times every 5 seconds

if4-mtu-change02    2  TPASS  :  Test is finished correctly.

<<<execution_status>>>

tag=if6-updown stime=1359722982

cmdline=" if6-updown"

contacts=""

analysis=exit

<<<test_output>>>

if6-updown01    0  TINFO  :  Verify the IPv6 connectivity is not broken when the ifconfig command ups, then downs an interface 128 times

if6-updown01    1  TPASS  :  Test is finished successfully.

if6-updown02    0  TINFO  :  Verify the IPv6 connectivity is not broken when the ip command ups, then downs an interface 128 times

if6-updown02    2  TPASS  :  Test is finished successfully.

incrementing stop

<<<execution_status>>>

initiation_status="ok"

duration=1449 termination_type=exited termination_id=0 corefile=no

cutime=103 cstime=456

<<<test_end>>>

 

Could you please let me know that above code changes are valid or not ? Please suggest me if there are any other solutions to resolve above error.

Any help would be appreciated !!!!

 

Thanks,

Bhushan 

 
 

Information transmitted by this e-mail is proprietary to MphasiS, its associated companies and/ or its customers and is intended 
for use only by the individual or entity to which it is addressed, and may contain information that is privileged, confidential or 
exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded 
to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly 
prohibited. In such cases, please notify us immediately at mailmaster@mphasis.com and delete this mail from your records.

[-- Attachment #1.2: Type: text/html, Size: 15051 bytes --]

[-- Attachment #2: Type: text/plain, Size: 238 bytes --]

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan

[-- 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

^ permalink raw reply	[flat|nested] 4+ messages in thread