Bug 223 – Regression using other than mercurial traces no longer works

Bug 223 - Regression using other than mercurial traces no longer works

Summary:

Regression using other than mercurial traces no longer works

Status:	RESOLVED FIXED

Product:	ns-3
Component:	build system
Version:	pre-release
Platform:	All All

Importance:	P1 blocker
Assigned To:	ns-bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-06-17 22:07 EDT by Craig Dowell
Modified:	2008-07-01 13:32 EDT (History)

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 From Craig Dowell 2008-06-17 22:07:03 EDT

Somewhen along the line, the regression tests that use traces from the
www.nsnam.org/releases directory stopped working.  Wscript gives python error
(urllib not imported), transfers bits but uses wrong names.

Its completely busted now.

------- Comment #1 From Gustavo J. A. M. Carneiro 2008-06-18 13:05:06 EDT -------

just missing import; should be fixed now.

------- Comment #2 From Craig Dowell 2008-06-18 15:40:48 EDT -------

The import urllib was a minor detail.  There were larger issues about getting
the names correct when pulling traces from the web.

It's all sorted out now, so I'll just leave it closed.  

Now, the VERSION file is used to drive all of the building of tarballs
(including traces) and it is used when downloading from the web and from
mercurial.  You will now see ns-3-dev-ref-traces in your regression directory
when you're working with mercurial and ns-3-dev.  You will now see
ns-3.1-RC1-ref-traces when you're working with released versions in either
mercurial or web.

Web regressions now actually work.

------- Comment #3 From Gustavo J. A. M. Carneiro 2008-06-19 05:39:27 EDT -------

It _did_ work correctly for me after adding the missing import.  And without a
way to reproduce the problem, I had to close the bug.