Opened 7 months ago

Last modified 7 weeks ago

#28170 assigned enhancement

Test stem pull requests against all supported tor versions, and tor nightly builds

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Stem Version:
Severity: Normal Keywords: ci, travis, 035-deferred-20190115, 041-proposed, teor-unreached-2019-03-08
Cc: teor Actual Points:
Parent ID: #29729 Points:
Reviewer: Sponsor:

Description

In #27913, we want to test stem against all supported tor versions, and tor nightly.

Child Tickets

Change History (8)

comment:1 Changed 7 months ago by atagar

Hi teor, what is the ask from me on this?

comment:2 in reply to:  1 Changed 7 months ago by teor

Replying to atagar:

Hi teor, what is the ask from me on this?

We want to make sure that changes to stem master don't break tor's CI. (I realise it's usually the other way around.)

I'm going to write a patch to chutney to test against all supported tor versions and tor nightly (see #28170). Then I'll copy the tor version matrix into stem's travis CI config, and update this ticket with the branch.

If you could review and merge my patch to stem's travis ci config, that would be great.

comment:3 Changed 7 months ago by atagar

We want to make sure that changes to stem master don't break tor's CI.

Gotcha. I should be made aware of regressions on my side by Stem's Jenkins runs. That tests against tor's tip (not against multiple tor versions) but I've found this tends to be sufficient for bugs on my end.

https://jenkins.torproject.org/job/stem-tor-ci/

Then I'll copy the tor version matrix into stem's travis CI config, and update this ticket with the branch.

Sorry, not sure I quite follow. Tor uses travis, but I don't for Stem.

comment:4 Changed 7 months ago by nickm

Parent ID: #27913

comment:5 in reply to:  3 Changed 7 months ago by teor

Replying to atagar:

We want to make sure that changes to stem master don't break tor's CI.

Gotcha. I should be made aware of regressions on my side by Stem's Jenkins runs. That tests against tor's tip (not against multiple tor versions) but I've found this tends to be sufficient for bugs on my end.

https://jenkins.torproject.org/job/stem-tor-ci/

Then I'll copy the tor version matrix into stem's travis CI config, and update this ticket with the branch.

Sorry, not sure I quite follow. Tor uses travis, but I don't for Stem.

The stem repository contains a travis config, and it runs under the torproject's travis:
https://travis-ci.org/torproject/stem

comment:6 Changed 4 months ago by nickm

Keywords: 035-deferred-20190115 041-proposed added
Milestone: Tor: 0.3.5.x-finalTor: unspecified

These tickets are all deferred from 0.3.5, since they are about updating CI and/or chutney settings.

comment:7 Changed 3 months ago by teor

Keywords: teor-unreached-2019-03-08 added
Owner: teor deleted

I'd like to do these tickets, but not in the next few months.

comment:8 Changed 7 weeks ago by teor

Parent ID: #29729

We might have diagnosed #29437 faster if we ran Stem CI with python 3.6 and any supported tor version.

Once I finish #29729, I can copy chutney's Travis config to a Stem PR, and then drop in the stem test commands.

Note: See TracTickets for help on using tickets.