relay: Reachability test is logged every second

A relay that auto discovers an IPv6 that is not reachable will attempt to launch a reachability test every second which creates a circuit each time.

From the info logs, it appears we might have a feedback loop between IPv4 bandwidth test and IPv6 reachability test (that should in the end never succeed).

There is this pattern every second:

Jul 24 14:11:53.316 [info] router_do_orport_reachability_checks(): Testing bandwidth of my IPv4 ORPort: 66.70.207.168:10001.
Jul 24 14:11:53.316 [info] origin_circuit_new(): Circuit 597 chose an idle timeout of 2445 based on 2330 seconds of predictive building remaining.
Jul 24 14:11:53.321 [info] onion_pick_cpath_exit(): Using requested exit node '$27F3833453C4006DF1E21C6BF62E4FCD8E99DEF2~WhatsGoingOn at 66.70.207.168'
Jul 24 14:11:53.328 [info] extend_info_from_node(): Including Ed25519 ID for $64A0B5722613DDFC2EB84897C550FBF4A096DE0D~NeyamRelay at 51.15.122.103
Jul 24 14:11:53.335 [info] extend_info_from_node(): Including Ed25519 ID for $77A56CB237740E24AEA2D61C8C8936232AFC1BD8~TheEpTicZeus at 54.36.227.247 and [2001:41d0:800:3a7::]
Jul 24 14:11:53.335 [info] circuit_send_first_onion_skin(): First hop: finished sending CREATE cell to '$64A0B5722613DDFC2EB84897C550FBF4A096DE0D~NeyamRelay at 51.15.122.103'
Jul 24 14:11:53.335 [info] router_do_orport_reachability_checks(): Testing reachability of my IPv6 ORPort: [<IPv6>]:10001.
Jul 24 14:11:53.335 [notice] Now checking whether IPv6 ORPort [<IPv6>]:10001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)

Might be that circuit_testing_opened() keeps on asking for an IPv6 reachability test everytime the IPv4 bandwidth circuit test opens?

Or else there is a feedback loop somehow with circuit_build_no_more_hops() that calls router_do_reachability_checks() if not all ORPort are reachable?

Attaching a snippet of info.log showing that problem.

info.log