Opened 3 years ago

Last modified 2 years ago

#20046 new defect

Test hidden services with different consensuses

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-hs, testing, chutney, consensus integration-testing
Cc: Actual Points:
Parent ID: Points: 2
Reviewer: Sponsor:

Description

Hidden service clients used to behave differently depending on which consensus they had (#20012). It was a bug, so we're going to remove it.

But the general issue remains: this code was never tested well, because chutney doesn't support testing clients and hidden services with different consensuses, and we never wrote unit tests for this, either.

This would be a great test to have for prop224 hidden services.

Child Tickets

Change History (4)

comment:1 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:2 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:3 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:4 Changed 2 years ago by nickm

Keywords: chutney consensus integration-testing added; 030-proposed removed
Note: See TracTickets for help on using tickets.