[Ns-developers] output of ./waf --regression

[Tom Henderson]

Mathieu Lacage wrote:
> hi,
> 
> I just noticed that the output of ./waf --regression is a bit more
> verbose than it should be:
> 
> [mathieu at localhost ns-3-dev]$ ./waf --regression
> Entering directory `/home/mathieu/code/ns-3-dev/build'
> Compilation finished successfully 
> ========== Running Regression Tests ==========
> Synchronizing reference traces using Mercurial.
> Pulling http://code.nsnam.org/ns-3-dev-ref-traces from repo.
> PASS test-csma-bridge
> PASS test-csma-broadcast
> PASS test-csma-multicast
> PASS test-csma-one-subnet
> PASS test-csma-packet-socket
> PASS test-csma-ping
> PASS test-csma-raw-ip-socket
> PASS test-csma-star
> PASS test-dynamic-global-routing
> PASS test-global-routing-slash32
> PASS test-ns2-mob
> PASS test-realtime-udp-echo
> Note the 3 messages below
> Sent 1024 bytes to 10.1.2.4
> Received 1024 bytes from 10.1.1.1
> Received 1024 bytes from 10.1.2.4
> PASS test-second
> PASS test-simple-error-model
> PASS test-simple-global-routing
> PASS test-simple-point-to-point-olsr
> PASS test-static-routing-slash32
> PASS test-tcp-large-transfer
> Skipping tcp-nsc-lfn: NSC not available.
> SKIP test-tcp-nsc-lfn
> And here again
> Sent 1024 bytes to 10.1.2.4
> Received 1024 bytes from 10.1.3.3
> Received 1024 bytes from 10.1.2.4
> PASS test-third
> PASS test-udp-echo
> PASS test-wifi-wired-bridging
> [mathieu at localhost ns-3-dev]$ 
> 
> Did I misconfigure my system or is this expected ? If not, I will file a
> bug.

these are artifacts of tutorial scripts second.cc and third.cc being 
added to the regression tests, and these tutorial scripts make use of 
the logging facilities.  These could probably be quieted in the 
regression by adding an option to disable logging and plumbing it into 
the regression test-second.py.

Tom