[Ns-developers] release update

[Mathieu Lacage]

On Fri, 2009-06-05 at 16:49 -0700, craigdo at ee.washington.edu wrote:

> 2) I have decided that it is too painful to do all of the test running
> inside waf, so I have packed up and moved into a new test.py
> that drives the testing process.  I expect that people will clone
> ns-3-allinone, then ./download.py, ./build.py and ./test.py.
> 
> Initially test.py will call ./waf check and ./waf --regression for
> thoroughness, but that should eventually go away.
> 
> The code in test.py runs tests in parallel based on the number of
> processors in the system.  It's really quite simple and much
> easier to understand than, well, anything in waf.  

I personally don't care much how the test execution is implemented but I
think that it makes sense to keep the current user interface to
executing tests, that is, make "./waf check" run the tests. I am sure
gustavo will be happy to make "./waf check" execute first your script in
utils/test.py and then, execute the equivalent of --regression. If
needed (that is, gustavo has no time to do this), I will take care of
this myself before the release. In time, if gustavo wants to make this
more integrated in waf by rewriting it using waf tasks, he will be free
to do so.

To summarize, if you don't want to deal with waf, don't deal with it,
but, please, move your script to ns-3-dev/utils/test.py and don't make
it do anything but execute your test binary: this will make it easier
for me to make the buildbot machinery run these tests.

Mathieu