bridge authorities mark every bridge stable+guard

Tonga lists every bridge as Stable and Guard.

Nick suggests this is because "bridge authorities don't count a bridge as having Failed for MTBF purposes when they find it to be non-Running"

[Automatically added by flyspray2trac: Operating System: All]

changed milestone to %Tor: unspecified

added TorCoreTeam201605 bridges component::core tor/tor milestone::Tor: unspecified owner::sysrqb performance priority::very low resolution::fixed severity::normal status::closed tor-bridge type::defect version::0.2.1.19 labels

This ought to be as simple as adding appropriate calls to the rephist_note_* commands in our bridge testing code.

Trac:
Milestone: N/A to N/A
Parent: N/A to N/A
Keywords: N/A deleted, N/A added

one question though... does this actually affect anything? It seems totally harmless.

Trac:
Description: Tonga lists every bridge as Stable and Guard.

Nick suggests this is because "bridge authorities don't count a bridge as having Failed for MTBF purposes when they find it to be non-Running"

[Automatically added by flyspray2trac: Operating System: All]

to

Tonga lists every bridge as Stable and Guard.

Nick suggests this is because "bridge authorities don't count a bridge as having Failed for MTBF purposes when they find it to be non-Running"

[Automatically added by flyspray2trac: Operating System: All]
Milestone: N/A to Tor: 0.2.3.x-final
Priority: minor to trivial

bridgedb has rules like "make sure at least one of the bridges you give out has the Stable flag". So since they all do, that rule is moot.

(It's possible this feature never got implemented, or not implemented like that. See #1606 (moved).

Trac:
Actualpointsdone: N/A to N/A
Actualpoints: N/A to N/A
Pointsdone: N/A to N/A
Points: N/A to N/A
Priority: trivial to normal

Trac:
Component: Tor Relay to Tor Bridge

Trac:
Keywords: N/A deleted, performance bridges added

Trac:
Milestone: Tor: 0.2.3.x-final to Tor: unspecified

Trac:
Priority: normal to trivial

Trac:
Keywords: performance bridges deleted, performance bridges tor-bridge added

Trac:
Component: Tor Bridge to Tor

I don't think this is true anymore...close?

Still true.

Show me a bridge that has the Running and Valid flag, in Tonga's bridge networkstatus file, that doesn't also have the Fast, Guard, and Stable flags?

Ah ha! That isn't what I thought this was.

Indeed it does appears that Running and Valid imply Fast Guard Stable. Small snippet (but it holds true for the rest).

s Fast Guard Running Stable Valid
s Valid
s Fast Guard Running Stable Valid
s Fast Guard Running Stable Valid
s Fast Guard Running Stable Valid
s Fast Guard Running Stable Valid
s
s Fast Guard Running Stable Valid
s Fast Guard Running Stable Valid
s Fast Guard Running Stable Valid
s Running
s Fast Guard Running Stable Valid
s Fast Guard Running Stable Valid
s Valid
s Valid

#9859 (moved) says that it fixed this bug.

Are we leaving the ticket open until we've put out 0.2.5.2-alpha, Tonga has upgraded, and we've confirmed? If that's the case, it sounds like a better plan would be to close the ticket because we think we fixed the bug, and reopen it later if needed.

(Also, yay!)

Trac:
Cc: arma,nickm,karsten to arma, nickm, karsten

I just checked a networkstatus from Tonga and this one looks good. Closing!

Trac:
Resolution: None to fixed
Sponsor: N/A to N/A
Severity: N/A to Normal
Status: new to closed
Reviewer: N/A to N/A

Trac:
Status: closed to reopened
Resolution: fixed to N/A

Trac:
Owner: N/A to sysrqb
Status: reopened to assigned

Trac:
Keywords: performance bridges tor-bridge deleted, performance bridges tor-bridge TorCoreTeam201605 added
Status: assigned to closed
Resolution: N/A to fixed

closed

mentioned in issue #1294 (moved)

mentioned in issue #9859 (moved)

moved to tpo/core/tor#1117 (closed)