[Ns-developers] Ns-3 Regression Testing Pushed

[Tom Henderson]

craigdo at ee.washington.edu wrote:
> Okay folks, the regression tests are pushed to ns-3-dev.
> 
> This means that before you check something in, you should change into the
> regression directory and run the regression tests using,
> 
>   python regression.py
> 
> and make sure nothing got busted.  You also might want to run this *before*
> you make a change so you don't end up debugging someone else's regression
> :-)
> 

Craig, sorry for the late comments, can you make a few enhancements?

- we discussed running the tests under valgrind (if valgrind is 
available on the system).  --command-template="valgrind --leak-check=full"

If valgrind is not found, it might help to print out a one-line debug 
statement that "valgrind not found on this system; running checks 
without it" as a hint to users that they may want to install it.

- it seems that if one runs regression.py on an unbuilt, freshly checked 
out repository, the script dies during configure, which ought to be 
fixed (I tried this on ns-regression)

- also, I think it would be preferable by default if things were rerun 
with optimized build.  Maybe if debug build passes all tests, repeat 
with optimized build?

- could the script catch a control-c and exit immediately?

- it would be nice if the output were teed to a file such as 
regression/regression.out, and maybe just append the output of the unix 
date command at the top of the file

Thanks,
Tom