When relays reset bandwidth tests, the test waits until the next directory document is received
When Tor is doing its first ORPort reachability test, it initiates one testing circuit after the first successful circuit, then one testing circuit per second until the ORPort is found reachable. Then it gives up after 20 minutes. (1200 circuits is too many.)
When tor receives any descriptor or consensus, it does another ORPort reachability test, and initiates a testing circuit.
When a testing circuit opens, and there aren't enough testing circuits to test bandwidth, then tor initiates another testing circuit.
But no testing circuits are opened after the bandwidth tests are reset.
So tor waits for the next directory document before doing a bandwidth test. We should just lunacy the tests straight away.
This is a bug on the original feature in commit 769f9201 in 0.1.2.2-alpha.