Opened 9 months ago

Closed 9 months ago

#29011 closed enhancement (wontfix)

PrivCount proof of concept: work out how to do integration testing without chutney

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: 0.4.1.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: privcount, 040-unreached-20190109, 041-accepted-20190115
Cc: Actual Points:
Parent ID: #27908 Points: 3
Reviewer: Sponsor: SponsorV


Tor and chutney can be unreliable, so we might need to do integration tests on PrivCount without chutney.

Here's one possible design:

  • split PrivCount into generic rust modules, tor-specific rust modules, and tor interface modules
  • create a command-line interface to the generic rust modules and tor-specific rust modules, which takes events, writes results, and aggregates results from files
  • use these file-based interfaces to integration test the non-tor, non-network PrivCount code

Child Tickets

Change History (7)

comment:1 Changed 9 months ago by teor

Type: defectenhancement

These should all be enhancements

comment:2 Changed 9 months ago by teor

Points: 3

We'd be starting from scratch, so this might take a few days.

comment:3 Changed 9 months ago by teor

Keywords: 040-unreached-20190109 041-proposed added
Milestone: Tor: 0.4.0.x-finalTor: unspecified

These tasks are on the 0.4.1 roadmap for PrivCount and Sponsor V.

comment:4 Changed 9 months ago by teor

Keywords: 041-proposed-on-roadmap added; 041-proposed removed
Milestone: Tor: unspecifiedTor: 0.4.1.x-final

Let's review these tickets at the next meeting using our 041-proposed process.

They're on the roadmap, so the review should focus on ticket size and team capacity (and sponsor expectations).

comment:5 Changed 9 months ago by teor

Keywords: 041-accepted-20190115 added; 041-proposed-on-roadmap removed

These PrivCount tickets are on the 041 roadmap, we accepted their points estimates in 041 without discussion.

comment:6 Changed 9 months ago by nickm

Sponsor: SponsorV

comment:7 Changed 9 months ago by nickm

Resolution: wontfix
Status: newclosed

Calling this a wontfix in favor of with-chutney solutions.

Note: See TracTickets for help on using tickets.