Chutney issueshttps://gitlab.torproject.org/tpo/core/chutney/-/issues2020-08-14T12:40:05Zhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/33231Prop 311: 6.3. Test Legacy Relays Accept IPv6 Extends using Chutney2020-08-14T12:40:05ZteorProp 311: 6.3. Test Legacy Relays Accept IPv6 Extends using ChutneyThis ticket depends on relay IPv6 extends in legacy/trac#33220. We may also need to disable the "Relay=3" protocol version check.
Test IPv6 extends from newer relays (which implement proposal 311) to older relays (which do not).
Althou...This ticket depends on relay IPv6 extends in legacy/trac#33220. We may also need to disable the "Relay=3" protocol version check.
Test IPv6 extends from newer relays (which implement proposal 311) to older relays (which do not).
Although proposal 311 does not create these kinds of circuits, we need to check for bugs and excessive logs in older tor versions.
See proposal 311, section 6.3:
https://gitweb.torproject.org/torspec.git/tree/proposals/311-relay-ipv6-reachability.txt#n698Tor: unspecifiedhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/33230Prop 311: 6.1. Ask Relay Operators to Test IPv6 Reachability2020-08-07T13:16:23ZteorProp 311: 6.1. Ask Relay Operators to Test IPv6 ReachabilitySee legacy/trac#33229 for advice on testing stages.
Write an email to the tor-relays list, asking relay operators to help test the proposal 311 IPv6 ORPort Reachability and Extends changes.
Once these changes are merged, volunteer rela...See legacy/trac#33229 for advice on testing stages.
Write an email to the tor-relays list, asking relay operators to help test the proposal 311 IPv6 ORPort Reachability and Extends changes.
Once these changes are merged, volunteer relay and bridge operators will be able to test them by:
* compiling from source,
* running nightly builds, or
* running alpha releases.
See proposal 311, section 6.1, relay operator test part:
https://gitweb.torproject.org/torspec.git/tree/proposals/311-relay-ipv6-reachability.txt#n671Sponsor 55: Improving the Tor network’s IPv6 supportNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/33229Prop 311: 6.1. Test IPv6 ORPort Reachability on the Tor Network2020-07-28T15:02:26ZteorProp 311: 6.1. Test IPv6 ORPort Reachability on the Tor NetworkTest the IPv6 ORPort Reachability and Extends changes in proposal 311, on the public tor network, with a small number of relays and bridges.
We can do public tests after each major feature is merged. We can
also wait for multiple featur...Test the IPv6 ORPort Reachability and Extends changes in proposal 311, on the public tor network, with a small number of relays and bridges.
We can do public tests after each major feature is merged. We can
also wait for multiple features to merge, and test them all.
Here are some useful features that we can test:
legacy/trac#33222 / legacy/trac#33226 IPv6 ORPort Reachability Self-Tests / Relay=3 Protocol
legacy/trac#33223 Don't Publish Descriptor if IPv6 ORPort is Unreachable
See proposal 311, section 6.1, initial public test part:
https://gitweb.torproject.org/torspec.git/tree/proposals/311-relay-ipv6-reachability.txt#n671Sponsor 55: Improving the Tor network’s IPv6 supportNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/33604Catch common runtime errors in chutney shell scripts2020-07-23T20:31:12ZteorCatch common runtime errors in chutney shell scriptsLet's gradually convert our scripts to use:
```
set -e
set -u
set -o pipefail
```
And maybe:
```
IFS=$'\n\t'
```
These settings help catch common errors in bash scripts at runtime:
http://redsymbol.net/articles/unofficial-bash-strict-m...Let's gradually convert our scripts to use:
```
set -e
set -u
set -o pipefail
```
And maybe:
```
IFS=$'\n\t'
```
These settings help catch common errors in bash scripts at runtime:
http://redsymbol.net/articles/unofficial-bash-strict-mode/
(Shellcheck helps us catch errors while writing scripts, but it can't help with runtime failures.)
Follow-up to legacy/trac#33451.https://gitlab.torproject.org/tpo/core/chutney/-/issues/16949Make Chutney Easier to Use & More Functional, Write Guide2020-07-23T20:13:24ZteorMake Chutney Easier to Use & More Functional, Write GuideI (teor) am writing a guide to using chuntney.
As part of that, I'm making chuntey easier to use, mainly through a series of tweaks that simplify usage and improve test coverage.
See https://trac.torproject.org/projects/tor/wiki/doc/Tor...I (teor) am writing a guide to using chuntney.
As part of that, I'm making chuntey easier to use, mainly through a series of tweaks that simplify usage and improve test coverage.
See https://trac.torproject.org/projects/tor/wiki/doc/TorChutneyGuide and the child tickets for more details.https://gitlab.torproject.org/tpo/core/chutney/-/issues/17277Chutney tests should include misbehaving clients and servers2020-06-27T13:18:59ZNick MathewsonChutney tests should include misbehaving clients and serversNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/29024Add pluggable-transport support to Chutney2020-06-27T13:18:43ZNick MathewsonAdd pluggable-transport support to ChutneyWe need to make PTs in general, and Snowflake in particular, more reliable and well-tested. On way to do that is with realistic integration tests, using Chutney.We need to make PTs in general, and Snowflake in particular, more reliable and well-tested. On way to do that is with realistic integration tests, using Chutney.Tor: 0.4.2.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/30826Chutney travis: remove 0.3.4, add 0.4.12020-06-27T13:18:37ZNick MathewsonChutney travis: remove 0.3.4, add 0.4.1The 0.4.1 branch is now separate; the 0.3.4 branches are now deprecated. We should update Chutney's travis configuration accordingly.The 0.4.1 branch is now separate; the 0.3.4 branches are now deprecated. We should update Chutney's travis configuration accordingly.Tor: unspecifiedhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/32630Chutney Travis: Make chutney work on Bionic images2020-06-27T13:18:36ZteorChutney Travis: Make chutney work on Bionic imagesIf we fix legacy/trac#32240 in Tor, we should do the same thing for Chutney's Travis config.If we fix legacy/trac#32240 in Tor, we should do the same thing for Chutney's Travis config.teorteorhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/32631Chutney Travis: Use the latest dependencies2020-06-27T13:18:36ZteorChutney Travis: Use the latest dependenciesUse the latest dependencies in Chutney Travis:
* Linux and macOS images
* tor versions
* python versionsUse the latest dependencies in Chutney Travis:
* Linux and macOS images
* tor versions
* python versionsteorteorhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/32731Add __future__ imports to every chutney python file2020-06-27T13:18:36ZteorAdd __future__ imports to every chutney python fileTo make extra sure any changes to our python 2.7 code are compatible with python 3, we should add `__future__` imports to every chutney python file.To make extra sure any changes to our python 2.7 code are compatible with python 3, we should add `__future__` imports to every chutney python file.teorteorhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/32758Travis: Update the macOS image for chutney2020-06-27T13:18:36ZteorTravis: Update the macOS image for chutneyteorteorhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/32775Remove 0.2.9 from chutney's CI2020-06-27T13:18:36ZteorRemove 0.2.9 from chutney's CIOn 1 January 2020, we won't be supporting 0.2.9 any more.On 1 January 2020, we won't be supporting 0.2.9 any more.https://gitlab.torproject.org/tpo/core/chutney/-/issues/32820Move the chutney pypy jobs to 0.4.2 xenial2020-06-27T13:18:36ZteorMove the chutney pypy jobs to 0.4.2 xenialTor master will soon be unsupported on Travis xenial, because Travis xenial only has OpenSSL 1.1.0. (See legacy/trac#31820.)
So we need to move the pypy jobs to Tor 0.4.2 xenial, because pypy isn't packaged for Travis Bionic yet.Tor master will soon be unsupported on Travis xenial, because Travis xenial only has OpenSSL 1.1.0. (See legacy/trac#31820.)
So we need to move the pypy jobs to Tor 0.4.2 xenial, because pypy isn't packaged for Travis Bionic yet.teorteorhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/33163Update list of Tor versions in Chutney's Travis CI2020-06-27T13:18:35ZteorUpdate list of Tor versions in Chutney's Travis CI* 0.2.9 and 0.4.0 are unsupported
* 0.4.2 is stable* 0.2.9 and 0.4.0 are unsupported
* 0.4.2 is stableteorteorhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/33267Prop 313: 8.1. Test IPv6 Relay Consensus Counts using Chutney2020-06-27T13:18:34ZteorProp 313: 8.1. Test IPv6 Relay Consensus Counts using ChutneyTest the IPv6 relay count script in proposal 313, using chutney networks.
Since chutney creates a limited number of relays, we also need to test these changes on consensuses from the public tor network. So we shouldn't spend much time t...Test the IPv6 relay count script in proposal 313, using chutney networks.
Since chutney creates a limited number of relays, we also need to test these changes on consensuses from the public tor network. So we shouldn't spend much time testing the script with chutney.
See proposal 313, section 8.1, chutney tests part:
https://gitweb.torproject.org/torspec.git/tree/proposals/313-relay-ipv6-stats.txt#n337Tor: 0.4.4.x-finalteorteorhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/33271Prop 313: 8.2. Test IPv6 Statistics using Chutney2020-06-27T13:18:33ZteorProp 313: 8.2. Test IPv6 Statistics using ChutneyWe want to test IPv6 connection and consumed bandwidth statistics using
chutney networks. However, chutney runs for a short amount of time, and
creates a limited amount of traffic, so we also need to test these changes
on the public tor ...We want to test IPv6 connection and consumed bandwidth statistics using
chutney networks. However, chutney runs for a short amount of time, and
creates a limited amount of traffic, so we also need to test these changes
on the public tor network.
In particular, we have struggled to test statistics using chutney, because
tor's hard-coded statistics period is 24 hours. (And most chutney networks
run for under 1 minute.)
Maybe we can change the statistics interval to 10-30 seconds, and see if that works?
See proposal 313, section 8.2, chutney tests part:
https://gitweb.torproject.org/torspec.git/tree/proposals/313-relay-ipv6-stats.txt#n355Tor: 0.4.4.x-finalteorteorhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/33353Split chutney's diagnostics into a new script2020-06-27T13:18:33ZteorSplit chutney's diagnostics into a new scriptChutney's failure diagnostics are currently in the Travis CI config file.
But we want to use them in tor's CI. And maybe chutney users want to use them as well.Chutney's failure diagnostics are currently in the Travis CI config file.
But we want to use them in tor's CI. And maybe chutney users want to use them as well.Sponsor 55: Improving the Tor network’s IPv6 supportteorteorhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/33376Update the networks in Chutney's CI to match Tor's new test-network*2020-06-27T13:18:33ZteorUpdate the networks in Chutney's CI to match Tor's new test-network*We need to update the list of chutney networks in chutney's CI, to match the networks we added to Tor's `make test-network` and `make test-network-all` in legacy/trac#33334.We need to update the list of chutney networks in chutney's CI, to match the networks we added to Tor's `make test-network` and `make test-network-all` in legacy/trac#33334.Sponsor 55: Improving the Tor network’s IPv6 supportteorteor