Bug 714 – TestSute ns3-tcp-cwnd fails

Bug 714 - TestSute ns3-tcp-cwnd fails


Summary:	TestSute ns3-tcp-cwnd fails

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	regression
Version:	pre-release
Hardware:	All All

Importance:	P1 blocker
Assigned To:	ns-bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-10-09 02:43 EDT by Craig Dowell
Modified:	2009-10-15 15:06 EDT (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Craig Dowell 2009-10-09 02:43:49 EDT

This is an artifact of the recent TCP patch.  Unknown whether or not this is a real failure.

happens on ns-regression:  configured for debug; gcc version 4.2.4 (Ubuntu
4.2.4-1ubuntu4); Linux version 2.6.24-19-server

reproduce with:

  ./waf --run "test-runner --suite=ns3-tcp-cwnd --basedir=`pwd`"

Comment 1 Josh Pelkey 2009-10-09 12:05:06 EDT

I looked at this a little bit a few days ago after I pushed the TCP patches.  To just relay some information for future reference to this bug, I compared the pcap files from the old (passing) testcase and the new (failing) test case.  I didn't look at every single packet in detail, but I believe they were identical (same number of packets, same time events, etc).

The testcase is failing because the total number of events is less than the expected 21.  It is instead 20.  So the last event that the testcase refers to (the "slamming shut" of the tcp cwnd) is not occuring.  I am unsure of whether or not this should actually happen.