Opened 7 months ago

Last modified 3 weeks ago

#27162 assigned enhancement

Travis: consider running CI on beta, nightly, and tor's lowest supported rust

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: 0.4.1.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: rust, tor-ci, privcount, 040-unreached-20190109, 041-accepted-20190115, teor-unreached-2019-03-08
Cc: dmr Actual Points:
Parent ID: Points: 1
Reviewer: Sponsor: SponsorV-can

Description (last modified by teor)

At the moment, Tor's Travis CI runs on stable rust, and our Appveyor (Windows) CI doesn't run rust at all (#26954).

But in our privcount_shamir work (#25669), we've discovered some important bugs by running beta and nightly.

Since Rust releases every 6 weeks, we should run CI on rust stable and beta, so that we catch any show-stoppers before they are stable.

We might also want to consider an allow_failures nightly build.

If we choose to support a lower version of rust than stable (when a major distro freezes on a lower version), we should also CI that version.

Child Tickets

Change History (12)

comment:1 Changed 7 months ago by teor

Summary: Travis: consider running CI on stable and beta rustTravis: consider running CI on beta, nightly, and tor's lowest supported rust

Fix title

comment:2 Changed 7 months ago by dmr

Cc: dmr added

comment:3 Changed 5 months ago by teor

Description: modified (diff)

Correct privcount shamir ticket.

comment:4 Changed 5 months ago by nickm

Milestone: Tor: 0.3.6.x-finalTor: 0.4.0.x-final

Tor 0.3.6.x has been renamed to 0.4.0.x.

comment:5 Changed 3 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:6 Changed 3 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:7 Changed 2 months ago by teor

Points: 0.5

comment:8 Changed 2 months ago by teor

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

We accepted this in the meeting.

comment:9 Changed 8 weeks ago by teor

Sponsor: SponsorV

This is sponsor V or sponsor 31.

comment:10 Changed 8 weeks ago by teor

Points: 0.51

comment:11 Changed 4 weeks ago by teor

Sponsor: SponsorVSponsorV-can

comment:12 Changed 3 weeks ago by teor

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

Unassign myself from -can tickets.

Note: See TracTickets for help on using tickets.