Require IPv6 tests in Travis CI

changed milestone to %Tor: 0.3.5.x-final

Trac:
Parent Ticket: #33050 (moved)

added actualpoints::0.7 chutney component::core tor/tor consider-backport-immediately ipv6 milestone::Tor: 0.3.5.x-final network-team-roadmap-2020Q1 owner::teor parent::33050 points::0.1 priority::medium resolution::fixed reviewer::nickm severity::normal sponsor::55-must status::closed tor-ci type::task labels

Trac:
Parent: #33194 (moved) to #33050 (moved)

We have active rust patches (and bugs) from two external contributors, so I can't make the rust jobs fast_finish.

We need to merge the #33075 (moved) backport, before making these changes.

We can delete the following redundant jobs:

Linux clang distcheck
- I think this job was actually an 0.2.9 merge forward error

We need to speed up the macOS chutney IPv6 job, because it runs for 23-46 minutes:

run IPv4-only in Linux, and IPv6-only in macOS

See my PRs:

Backport require IPv6 chutney to pass, remove a redundant job, reorder jobs (#33194 (moved) and #33195 (moved)):

0.3.5: https://github.com/torproject/tor/pull/1732
0.4.1: https://github.com/torproject/tor/pull/1733
0.4.2: https://github.com/torproject/tor/pull/1734
0.4.3: https://github.com/torproject/tor/pull/1735

Split IPv4 and IPv6 chutney tests, and only run IPv6 on macOS (#33280 (moved) and #33303 (moved)):

master: https://github.com/torproject/tor/pull/1731

I think it's worth backporting these changes, they are travis-only, and should make a significant difference to CI speeds during backport merges.

Trac:
Keywords: N/A deleted, ipv6, consider-backport-immediately added
Reviewer: N/A to nickm
Cc: N/A to nickm
Actualpoints: N/A to 0.6
Status: assigned to needs_review

There is also a master test branch, without #33280 (moved):

https://github.com/teor2345/tor/branches/all?query=33195

I've left comments on https://github.com/torproject/tor/pull/1731 .

As for backporting, I agree with backporting the travis changes, but: let's try them in master for a week or so before we backport, in case they turn out to have unforseen drawbacks.

Trac:
Status: needs_review to needs_revision

Thanks, I've quoted those variables, improved make's output, and improved the job display on Travis.

Trac:
Status: needs_revision to needs_review

Trac:
Actualpoints: 0.6 to 0.7

I just compared master and this PR:

Both finish in about 18 minutes, the IPv6-only tests take 12 minutes on macOS.

I think that's a win, because we:

added a slow chutney job (25-45 minutes), but made it faster (13 minutes), and
deleted a redundant distcheck job (8 minutes), but kept the same CI wall clock run time.

(The extra 5 minutes for the chutney job is hidden by the parallelism.)

LGTM. Let's merge this in into master and let it cook for a little while.

Trac:
Status: needs_review to merge_ready

Merged to master, because I needed it for #33334 (moved).

I had to re-do the #33280 (moved) and #33195 (moved) merge, because the "ours" merge deleted some commits that were merged into 0.4.3 after the branches split off from master.

Trac:
Keywords: consider-backport-immediately deleted, consider-backport-after-0433 added
Milestone: Tor: 0.4.4.x-final to Tor: 0.4.3.x-final

Merged to 0.3.5 and later, because I need it for #33048 (moved).

We also want to have consistent tor-chutney CI, particularly now that #33232 (moved) is merged.

Trac:
Milestone: Tor: 0.4.3.x-final to Tor: 0.3.5.x-final
Status: merge_ready to closed
Keywords: consider-backport-after-0433 deleted, consider-backport-immediately added
Resolution: N/A to fixed

Add all the tickets from sponsor 55 that are done and being worked on to the keyword #network-team-roadmap-2020Q1 so I can look at them in the wiki page...

Trac:
Keywords: N/A deleted, network-team-roadmap-2020Q1 added