[Ns-bugs] [Bug 489] New: ns-3-allinone inflexible WRT trace file location
code@nsnam.ece.gatech.edu
code at nsnam.ece.gatech.edu
Thu Feb 5 09:17:10 PST 2009
http://www.nsnam.org/bugzilla/show_bug.cgi?id=489
Summary: ns-3-allinone inflexible WRT trace file location
Product: ns-3
Version: pre-release
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P1
Component: build system
AssignedTo: ns-bugs at isi.edu
ReportedBy: craigdo at ee.washington.edu
Estimated Hours: 0.0
Created an attachment (id=372)
--> (http://www.nsnam.org/bugzilla/attachment.cgi?id=372)
Patch to make regression trace files specification possible
As it stands allinone is very inflexible about how you can specify a regression
trace file. This makes life difficult for automated testing.
For example, if you have a repository craigdo/ns-3-tap, download.py tries to
fetch http://code.nsnam.org/ns-3-tap-ref-traces. This is not desirable.
Often, you want to make changes to some code and make sure that the standard
reference traces are not affected. In this case you would want to fetch
ns-3-dev-ref-traces when your BRANCH is craigdo/ns-3-tap.
There needs to be a -r option in download.py to go along with the -n option,
which defaults to all the right things -- for example, using
ns-3-dev-ref-traces independent of your BRANCH as above.
Patch attached.
--
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Ns-bugs
mailing list