Opened 6 weeks ago
Last modified 3 weeks ago
#29010 assigned enhancement
PrivCount proof of concept: work out how to do CI for PrivCount using chutney
Reported by: | teor | Owned by: | teor |
---|---|---|---|
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 |
Description
We can do CI for PrivCount using chutney:
- launch a standard chutney network
- launch the Tally Reporter (TR)
- run some data through the network
- check the results using a chutney script
If we want to check extrainfo descriptors against PrivCount statistics, we'll need to publish them more often in test networks.
Child Tickets
Change History (6)
comment:1 Changed 6 weeks ago by
Type: | defect → enhancement |
---|
comment:2 Changed 6 weeks ago by
Points: | → 3 |
---|
This could take a few days, depending on how much we need to change in chutney.
comment:3 Changed 6 weeks ago by
Keywords: | 040-unreached-20190109 041-proposed added |
---|---|
Milestone: | Tor: 0.4.0.x-final → Tor: unspecified |
These tasks are on the 0.4.1 roadmap for PrivCount and Sponsor V.
comment:4 Changed 6 weeks ago by
Keywords: | 041-proposed-on-roadmap added; 041-proposed removed |
---|---|
Milestone: | Tor: unspecified → Tor: 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 5 weeks ago by
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 3 weeks ago by
Sponsor: | → SponsorV |
---|
These should all be enhancements