Skip to content
This repository has been archived by the owner. It is now read-only.

Bug28736 #313

Merged
merged 15 commits into from Dec 21, 2018
Merged

Bug28736 #313

merged 15 commits into from Dec 21, 2018

Conversation

Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

1 participant
@juga0
Copy link
Contributor

@juga0 juga0 commented Dec 9, 2018

No description provided.

juga0 added 15 commits Dec 9, 2018
The time it took to run prioritize function is not relevant for
the operator.
After several days, prioritiy would be adjusted for many relays,
so don't log it.
We can have different debug verbose levels in the future.
that would be shown at info level.
If rtt is configured to 0, the rtt measurements are not run,
but it was being logged that they're run
obtained when trying to build the circuit, or None if it was
successful.
That way it can be logged and stored in the results.
Warnings can make think the operator that sbws is not working,
while it's normal that some measurements fail.
Resultdump already logs at info level what succcess and what fails.
Keep these logs at debug level.
When a new loop starts and when it ends, with the number of relays
measured and the time it took.
since it takes some seconds and the operator would not see any
progress at the beginning, until relays start to be measured.
since it takes some seconds.
bandwidth or rtt, so that it can be used to be stored and logged.
The error that is returned by an exception, not a custom error.
So that it's easier to debug what fails.
Closes bug #28736. Bugfix v0.3.0.
@juga0 juga0 merged commit b250571 into torproject:master Dec 21, 2018
1 check passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.