Investigate if Chutney's network defaults fits the test suite needs
Originally created by @bertagaz on #11560 (Redmine)
While testing online scenarios and watching Tails’ Tor client logs, I often see that it has troubles to have enough directory informations to build a circuit. Its logs are filled with lines like:
[notice] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
Even after retry_tor(), this problem is not solved, and the scenario fails.
If one watch at the chutney Tor nodes logs, they are filled with auth directory votes and stuffs like that. At the moment, the consensus is set to last 20 seconds only (if I get it right), so the network load with this is pretty high, and it may be difficult for Tails’ Tor client to get a valid consensus.
The chutney settings are quite tight, and done so to stress test the fake Tor network and accelerate it. But for Tails tests, we want a stable Tor network, so we might want to have different settings.
I’ve had good results by setting V3AuthVotingInterval
to 600 (in place
of 10), but there may be other changes we may want to consider.