[tor-bugs] #6752 [Tor]: TestingTorNetwork doesn't lower the dir fetch retry schedules

[Tor Bug Tracker & Wiki]

#6752: TestingTorNetwork doesn't lower the dir fetch retry schedules
--------------------------------------+-------------------------------------
 Reporter:  arma                      |          Owner:                    
     Type:  enhancement               |         Status:  new               
 Priority:  major                     |      Milestone:  Tor: 0.2.4.x-final
Component:  Tor                       |        Version:                    
 Keywords:  tor-client small-feature  |         Parent:  #7172             
   Points:                            |   Actualpoints:                    
--------------------------------------+-------------------------------------

Comment(by arma):

 Replying to [comment:15 karsten]:
 > But before I write a patch, how would I reproduce the situation where
 clients don't bootstrap because of too high dir fetch retry schedules?

 My first suggestion would be to start your client before a consensus is
 available, i.e. before the directory authorities have computed a
 consensus. I expect your Tor client will try twice, and then wait a whole
 minute before trying a third time.

 A more realistic, but more subtle to reproduce case, would be one where
 there's a bug in Tor that prevents some of the directory mirrors or
 authorities from having a copy of the consensus. Then clients that try to
 bootstrap from those dir points will fail (nothing to get) and not retry
 on a proper time schedule.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6752#comment:21>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online