Opened 5 months ago

Closed 3 months ago

#30066 closed enhancement (fixed)

Write a script that tests chutney's major features on the specified network and tor version

Reported by: teor Owned by:
Priority: Medium Milestone:
Component: Core Tor/Chutney Version:
Severity: Normal Keywords: chutney-ci
Cc: gaba Actual Points: 1
Parent ID: Points: 1
Reviewer: Sponsor: Sponsor19

Description

We'd like to test each major chutney feature on each network (or each feature on at least one network).

To make this testing easier, we should have a script that tests each major feature. It should accept a network argument, and default to a network that covers most of tor's features.

We might also want to allow extra arguments to test-network.sh to be passed through to the script.

Child Tickets

TicketTypeStatusOwnerSummary
#20473defectclosedteorFix Chutney Nodes that don't bootstrap
#30070enhancementclosedAdd a chutney feature that prints the tor version

Change History (10)

comment:1 Changed 5 months ago by teor

Actual Points: 10.3
Reviewer: nickm
Status: assignedneeds_review

See my PR:
https://github.com/torproject/chutney/pull/22

I'm still working out how to match up networks and features.

comment:2 Changed 5 months ago by teor

Actual Points: 0.30.7

comment:3 Changed 5 months ago by teor

Status: needs_reviewneeds_revision

There are a lot of bugs in chutney/tor revealed by this test.
So I'm going to work on it a bit more tomorrow.

comment:4 Changed 5 months ago by teor

Keywords: network-team-roadmap-2019-Q1Q2 removed
Parent ID: #29729
Sponsor: Sponsor19Sponsor19-can
Summary: Write a script that tests chutney's major features on the specified networkWrite a script that tests chutney's major features on the specified network and tor version

The first commit in this PR contains a draft script:
https://github.com/torproject/chutney/pull/24

We should modify it to ask chutney for the tor version (#30070), and choose the right networks for that version.

We should also copy across the features and networks from the Travis CI config.

comment:5 Changed 5 months ago by teor

Reviewer: nickm
Status: needs_revisionnew

I don't intend to revise this patch any time soon.

comment:6 Changed 5 months ago by teor

Actual Points: 0.7
Owner: teor deleted
Status: newassigned

comment:7 Changed 3 months ago by gaba

Keywords: ex-sponsor-19 added

Adding the keyword to mark everything that didn't fit into the time for sponsor 19.

comment:8 Changed 3 months ago by gaba

Keywords: ex-sponsor19 added
Sponsor: Sponsor19-can

Remove sponsor 19 and add a keyword ex-sponsor19 to mark all the tickets that could have been in the scope of the sponsor.

comment:9 Changed 3 months ago by teor

Parent ID: #29267

We can do this eventually, but it's not urgent.

We might use pieces of it for #29267.

comment:10 Changed 3 months ago by teor

Actual Points: 1
Cc: gaba added; teor removed
Keywords: ex-sponsor-19 ex-sponsor19 removed
Parent ID: #29267
Resolution: fixed
Sponsor: Sponsor19
Status: assignedclosed

Hi Gaba, we merged this into chutney about a month ago as part of Sponsor 19.

Note: See TracTickets for help on using tickets.