Bug 1340 – ns3tcp-loss-test-suite.cc tests failing

Bug 1340 - ns3tcp-loss-test-suite.cc tests failing


Summary:	ns3tcp-loss-test-suite.cc tests failing

Status:	RESOLVED FIXED

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

Importance:	P5 normal
Assigned To:	Adrian S.-W. Tam

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2012-01-13 18:47 UTC by Tom Henderson
Modified:	2012-10-04 13:55 UTC (History)
CC List:	2 users (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 Tom Henderson 2012-01-13 18:47:31 UTC

fixing bug 1338 uncovered that some TCP tests now fail (which haven't been running since the waf upgrade).  These may be due to changed behavior prior to the ns-3.13 release.

these seem to be due to the TCP behavior changing and the need to generate new response vectors.  I stepped through the first test case in gdb and found that it kept with the response vector for many packets, and seemed to die at the end.   

These are disabled for now:

#if 0
  AddTestCase (new Ns3TcpLossTestCase ("Tahoe", 0));
  AddTestCase (new Ns3TcpLossTestCase ("Tahoe", 1));
  AddTestCase (new Ns3TcpLossTestCase ("Tahoe", 2));
  AddTestCase (new Ns3TcpLossTestCase ("Tahoe", 3));
  AddTestCase (new Ns3TcpLossTestCase ("Tahoe", 4));

  AddTestCase (new Ns3TcpLossTestCase ("Reno", 0));
  AddTestCase (new Ns3TcpLossTestCase ("Reno", 1));
  AddTestCase (new Ns3TcpLossTestCase ("Reno", 2));
  AddTestCase (new Ns3TcpLossTestCase ("Reno", 3));
  AddTestCase (new Ns3TcpLossTestCase ("Reno", 4));

  AddTestCase (new Ns3TcpLossTestCase ("NewReno", 0));
  AddTestCase (new Ns3TcpLossTestCase ("NewReno", 1));
  AddTestCase (new Ns3TcpLossTestCase ("NewReno", 2));
  AddTestCase (new Ns3TcpLossTestCase ("NewReno", 3));
  AddTestCase (new Ns3TcpLossTestCase ("NewReno", 4));
#endif

Comment 1 Brian Swenson 2012-10-04 13:55:18 UTC

Verified TCP functionality and generated new response-vectors for tests that were failing.

tcp-loss-Tahoe4
tcp-loss-NewReno2-4

changeset:  9101:ecaef72c8660