Re: [Cse461] discoverytest.fish output

• Previous message: Evan Martin: "[Cse461] help versus headphones"
• In reply to: Cameron Tom: "[Cse461] discoverytest.fish output"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Yikes! Good point. Yes, please do take out debug messages or change the
debug level when you run discoverytest.fish.

For the discoverytest, the output should be a few pages. Although we'd
like to see packet sends and receives in floodtest, for discoverytest,
just the lists of neighbors over time and the result of the two pings in
the script should suffice.

Cheers,
Janet

On Tue, 13 Jan 2004, Cameron Tom wrote:

> The output from discoverytest.fish is very long - over 200 pages for us.
> Therefore, can we:
> 1) Increase the time between neighbor discovery pings. We're using 10
> seconds right now.
> 2) Temporarily take out debug messages at our discretion or change the
> Debug reporting level for the purposes of this test.
>
> Also, how many pages of output should we aim for?
>
> Thanks,
> Cameron
>
> _______________________________________________
> Cse461 mailing list
> Cse461_at_cs.washington.edu
> http://mailman.cs.washington.edu/mailman/listinfo/cse461
>

-- 
Janet Davis
jlnd_at_cs.washington.edu
http://www.cs.washington.edu/homes/jlnd/
_______________________________________________
Cse461 mailing list
Cse461_at_cs.washington.edu
http://mailman.cs.washington.edu/mailman/listinfo/cse461

• Previous message: Evan Martin: "[Cse461] help versus headphones"
• In reply to: Cameron Tom: "[Cse461] discoverytest.fish output"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.6 : Tue Jan 13 2004 - 20:10:59 PST