[tor-bugs] #34088 [Core Tor/Tor]: circuit_build_times_update_alpha(): Bug: Could not determine largest build time

[Tor Bug Tracker & Wiki]

#34088: circuit_build_times_update_alpha(): Bug: Could not determine largest build
time
--------------------------+----------------------------------------
 Reporter:  s7r           |          Owner:  (none)
     Type:  defect        |         Status:  new
 Priority:  Medium        |      Milestone:
Component:  Core Tor/Tor  |        Version:  Tor: 0.4.4.0-alpha-dev
 Severity:  Normal        |     Resolution:
 Keywords:                |  Actual Points:
Parent ID:  #34082        |         Points:
 Reviewer:                |        Sponsor:
--------------------------+----------------------------------------
Description changed by s7r:

Old description:

> I don't think this is HSv3 ONLY related, but I can only make it happen
> while building large amounts of rendezvous circuits with reasonable
> concurrency (over 50). I am not assigning the tor-hs keyword for this
> reason, but sticking it to same master parent ticket.
>
> All lines are the same. It is seen for like 130-160 times during the
> build of little over 100.000 rendezvous circuits.
>
> {{{
> Apr 03 04:05:33.000 [warn] circuit_build_times_update_alpha(): Bug: Could
> not determine largest build time (0). Xm is 20025ms and we've abandoned 0
> out of 136 circuits. (on Tor 0.4.4.0-alpha-dev )
> Apr 03 04:05:33.000 [warn] circuit_build_times_update_alpha(): Bug: Could
> not determine largest build time (0). Xm is 20025ms and we've abandoned 0
> out of 137 circuits. (on Tor 0.4.4.0-alpha-dev )
> Apr 03 04:05:33.000 [warn] circuit_build_times_update_alpha(): Bug: Could
> not determine largest build time (0). Xm is 20025ms and we've abandoned 0
> out of 138 circuits. (on Tor 0.4.4.0-alpha-dev )
> Apr 03 04:05:33.000 [warn] circuit_build_times_update_alpha(): Bug: Could
> not determine largest build time (0). Xm is 20025ms and we've abandoned 0
> out of 139 circuits. (on Tor 0.4.4.0-alpha-dev )
> Apr 03 04:05:33.000 [warn] circuit_build_times_update_alpha(): Bug: Could
> not determine largest build time (0). Xm is 20025ms and we've abandoned 0
> out of 140 circuits. (on Tor 0.4.4.0-alpha-dev )
> }}}

New description:

 I don't think this is HSv3 ONLY related, but I can only make it happen
 while building large amounts of rendezvous circuits with reasonable
 concurrency (over 50). I am not assigning the tor-hs keyword for this
 reason, but sticking it to same master parent ticket.

 All lines are the same. It is seen for like 130-160 times during the build
 of little over 100.000 rendezvous circuits.

 {{{
 Apr 03 04:05:33.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 20025ms and we've abandoned 0
 out of 136 circuits. (on Tor 0.4.4.0-alpha-dev )
 Apr 03 04:05:33.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 20025ms and we've abandoned 0
 out of 137 circuits. (on Tor 0.4.4.0-alpha-dev )
 Apr 03 04:05:33.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 20025ms and we've abandoned 0
 out of 138 circuits. (on Tor 0.4.4.0-alpha-dev )
 Apr 03 04:05:33.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 20025ms and we've abandoned 0
 out of 139 circuits. (on Tor 0.4.4.0-alpha-dev )
 Apr 03 04:05:33.000 [warn] circuit_build_times_update_alpha(): Bug: Could
 not determine largest build time (0). Xm is 20025ms and we've abandoned 0
 out of 140 circuits. (on Tor 0.4.4.0-alpha-dev )
 }}}

 EDIT: All lines are the same except it always abandons 0 out of N circuits
 and N is always different of course, increasing with +1 most of the times
 until the Bug warn disappears.

--

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