[Swan-dev] testing noise

D. Hugh Redelmeier hugh at mimosa.com
Thu Jun 18 18:42:10 EEST 2015


I just completed another test run.  I don't know how well it did because 
I'm, as usual, daunted by the labour of understanding the noise.

I found the output of this command interesting:
	grep -h '^[+-]' */OUTPUT/*.diff | sort | uniq -c | sort -nr | less
It finds the changed lines, counts the duplication, and displays them
in order of descending frequency.

The top hits were:
   1384 +src 0.0.0.0/0 dst 0.0.0.0/0 
    960 +road #
    706 +       socket out priority 0 ptype main 
    706 +       socket in priority 0 ptype main 
    378 +west #
    290 +east #
    287 +rtt min/avg/max/mdev = 0.XXX/0.XXX/0.XXX/0.XXX ms
    262 +--- 192.1.2.23 ping statistics ---
    259 +2 packets transmitted, 2 received, 0% packet loss, time XXXX
    248 +000  
    130 +000 nhelpers=-1, uniqueids=yes, perpeerlog=no, shunt_lifetime=900
    129 -               proto esp reqid REQID mode tunnel
    125 -000  
    123 -               proto esp reqid REQID mode transport
    122 -       dir out priority 1568 ptype main 
    121 -       tmpl src 0.0.0.0 dst 0.0.0.0
    116 +==1181== 
    116 +==1178== 

Likely some of these are from bugs that I introduced.  Few jump out at
me though.

I'd expect a lot more of + and - lines to match up in count and
content.  Like these:
     38 -4 packets transmitted, 4 received, 0% packet loss, time XXXX
     38 +4 packets transmitted, 0 received, 100% packet loss, time XXXX
These are the first, and they are way down on the list at position 82.


More information about the Swan-dev mailing list