Opened 8 years ago

Closed 8 years ago

Last modified 7 years ago

#6169 closed defect (fixed)

Bug: CircuitBuildTime learning is not disabled. Consensus=0, Config=0, AuthDir=0, StateFile=0

Reported by: arma Owned by:
Priority: Low Milestone: Tor: 0.2.3.x-final
Component: Core Tor/Tor Version: Tor: 0.2.3.17-beta
Severity: Keywords: tor-client
Cc: andrea Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by arma)

I just recompiled the latest Tor master, and removed my previous circuit build times to induce Tor to make new circuits (to try to tickle bugs in the new #5458 code), and got

Jun 15 03:31:30.000 [info] or_state_load(): Loaded state from "/home/arma/.tor/state"
Jun 15 03:31:30.000 [debug] circuit_build_times_disabled(): Bug: CircuitBuildTime learning is not disabled. Consensus=0, Config=0, AuthDir=0, StateFile=0
Jun 15 03:31:30.000 [debug] circuit_build_times_disabled(): Bug: CircuitBuildTime learning is not disabled. Consensus=0, Config=0, AuthDir=0, StateFile=0
Jun 15 03:31:30.000 [info] circuit_build_times_parse_state(): Adding 0 timeouts.
Jun 15 03:31:30.000 [info] circuit_build_times_parse_state(): Loaded 0/0 values from 0 lines in circuit time histogram
Jun 15 03:31:30.000 [debug] circuit_build_times_disabled(): Bug: CircuitBuildTime learning is not disabled. Consensus=0, Config=0, AuthDir=0, StateFile=0

I get the 'Bug' line pretty often.

Child Tickets

Change History (8)

comment:1 Changed 8 years ago by arma

Description: modified (diff)

comment:2 Changed 8 years ago by arma

Summary: Bug: CircuitBuildTim e learning is not disabled. Consensus=0, Config=0, AuthDir=0, StateFile=0Bug: CircuitBuildTime learning is not disabled. Consensus=0, Config=0, AuthDir=0, StateFile=0

comment:3 Changed 8 years ago by mikeperry

Priority: normalminor

Is the bug here that the word "Bug:" should not be a prefix in the debug-level log messages? If so, this is minor.

comment:4 Changed 8 years ago by arma

The lines were added as part of 41a458ec

So I assumed she wanted to know if anybody encountered them.

The current meaning of LD_BUG is (was) "an event has occurred which the developers thought would never occur. They will want to know."

Did we change it to "this is a way to distinguish the log messages I wanted to see from the ones I didn't want to see"?

comment:5 Changed 8 years ago by nickm

The meaning of LD_BUG didn't change, but it looks like this one shouldn't have been an LD_BUG.

comment:6 Changed 8 years ago by nickm

Resolution: fixed
Status: newclosed

Fixed in 8030ec4f272d470b9d01b7095f17252aaca163c2

comment:7 Changed 7 years ago by nickm

Keywords: tor-client added

comment:8 Changed 7 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.