DD1984 / sockperf

Automatically exported from code.google.com/p/sockperf
Other
1 stars 0 forks source link

sockperf pp --tcp error and abort with burst -b1000 #3

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
imported from: http://argus-bg.dnsalias.org/issues/721
What steps will reproduce the problem?
1.sockperf sr --tcp
2.sockperf pp --tcp -i 1.1.1.28 -b 1000
3.(happend in some of the tests.  Need to check if this is still rellevant!

What is the expected output? What do you see instead?
client exits with the following error:
root@IBM29 vperf_2]# vperf pp --tcp -i 1.1.1.28 -b 1000
vperf: version #2.1.1801 
vperf: No VMA version info
vperf[CLIENT] send on:vperf: using recvfrom() to block on socket(s)

[ 0] IP = 1.1.1.28 PORT = 11111 # TCP
vperf: Warmup stage (sending a few dummy packets)...
vperf: Starting test...
vperf: PacketTimes.cpp:44:ERROR: _seqNo=2010186544 > m_maxSequenceNo=20001010
Please use labels and text to provide additional information.

Original issue reported on code.google.com by avne...@gmail.com on 29 Mar 2011 at 2:16

GoogleCodeExporter commented 9 years ago

Original comment by igor.ivanov@itseez.com on 29 Mar 2011 at 2:45

GoogleCodeExporter commented 9 years ago
Investigation note:
1. This issue was reproduced with vperf r1866;
2. Failure is appeared because of incorrect processing of data less than 12;
3. There is fix for this case in later versions;
4. successfully checked on r1870(vperf);
5. successfully checked on r33(sockperf);

Original comment by igor.ivanov@itseez.com on 30 Mar 2011 at 12:01

GoogleCodeExporter commented 9 years ago

Please don't use WontFix for this bug!

WontFix is only for bugs that we accept as bug and say that we'll not fix them. 
 (Hence, we agree to live with them).
For bugs, that you think they are not bugs you should set status to *Invalid*.
However, *this one is valid* (since the report relates to old vperf: 2.1.1801 
were the bug exists).  Hence, you should indicate it as *fixed*, if you think 
it was fixed as part of fixing other bug (probably, the code change for ret<0 ).
Anyhow, please verify it with other burst sizes.  Meny told me ~week ago that 
he encountered it with bursts of 10000.

Original comment by avne...@gmail.com on 30 Mar 2011 at 12:20

GoogleCodeExporter commented 9 years ago
r33 was verified using at least 1000 iterations with -b option in interval 
(1..100000)
r1870 was verified using at least 100 iterations with -b option in interval 
(1..100000)

Original comment by igor.ivanov@itseez.com on 30 Mar 2011 at 12:49

GoogleCodeExporter commented 9 years ago
then close it as Fixed.

Original comment by avne...@gmail.com on 30 Mar 2011 at 12:52

GoogleCodeExporter commented 9 years ago

Original comment by igor.ivanov@itseez.com on 31 Mar 2011 at 7:26