Chutney issueshttps://gitlab.torproject.org/tpo/core/chutney/-/issues2020-06-27T13:18:40Zhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/30066Write a script that tests chutney's major features on the specified network a...2020-06-27T13:18:40ZteorWrite a script that tests chutney's major features on the specified network and tor versionWe'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...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.https://gitlab.torproject.org/tpo/core/chutney/-/issues/30048Write a bwfile creation and validation test for chutney2020-07-23T20:48:43ZteorWrite a bwfile creation and validation test for chutneyChutney has a bwfile network, but the user has to create the actual file. And there are no tests.Chutney has a bwfile network, but the user has to create the actual file. And there are no tests.https://gitlab.torproject.org/tpo/core/chutney/-/issues/30211Work out why bridges+hs-v2 is unstable in CI2020-07-23T20:52:16ZteorWork out why bridges+hs-v2 is unstable in CIhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/29729Work out which networks to run in Chutney's CI2020-06-27T13:18:42ZteorWork out which networks to run in Chutney's CIWork out which networks to run, and if they should have separate jobs.
We don't need to test all the networks, just the ones that test chutney features. In particular, we don't need a tor version vs chutney network matrix: that should g...Work out which networks to run, and if they should have separate jobs.
We don't need to test all the networks, just the ones that test chutney features. In particular, we don't need a tor version vs chutney network matrix: that should go in the tor branch CI, not the chutney CI.
The default network should test as many of tor/chutney's features as possible. If this network breaks on a particular tor version, we look at that Tor version's CI to see which particular networks have broken.
Then we want a separate job for each separate feature:
* a bridge network from "make test-network-all"
* an onion service v2 and v3 network from "make test-network-all"
* an IPv6 network from "make test-network-all"
We can add other networks as needed:
* when we add new features to chutney, like PTs
* if we break existing features without breaking chutney's CI
* if we break tor's CI without breaking chutney's CIteorteorhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/29741Work out how to fail chutney travis jobs when the tor repository is out of da...2020-07-23T20:48:00ZteorWork out how to fail chutney travis jobs when the tor repository is out of date or missingIn legacy/trac#27912, we configure a bunch of deb lines that depend on deb.torproject.org. But what happens when the repository is updated after a release?
We can either:
* remember to update the travis config every release, or
* work o...In legacy/trac#27912, we configure a bunch of deb lines that depend on deb.torproject.org. But what happens when the repository is updated after a release?
We can either:
* remember to update the travis config every release, or
* work out how to make the jobs fail when they fall back to 0.2.9.14 (or Ubuntu security updates' current version)
Maybe there's a travis option that we could use?
This task does not need to be solved straight away.https://gitlab.torproject.org/tpo/core/chutney/-/issues/20409When some chutney tors die, clean up the rest2020-06-27T13:18:54ZteorWhen some chutney tors die, clean up the restChutney should clean up all the tor processes it starts, and leave all other processes alone.
I think this means adding `pkill -P $$` to the end of chutney/tools/test-network.sh , and making sure it's executed even if chutney returns fa...Chutney should clean up all the tor processes it starts, and leave all other processes alone.
I think this means adding `pkill -P $$` to the end of chutney/tools/test-network.sh , and making sure it's executed even if chutney returns failure.teorteorhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/22133When CHUTNEY_DEBUG is set, make tor log a debug log2020-07-23T20:32:29ZteorWhen CHUTNEY_DEBUG is set, make tor log a debug logWe can do this using similar code to legacy/trac#20409 and legacy/trac#21903.We can do this using similar code to legacy/trac#20409 and legacy/trac#21903.https://gitlab.torproject.org/tpo/core/chutney/-/issues/33615Wait for at least 60 seconds for 0.3.5 and earlier to bootstrap2020-06-27T13:18:31ZteorWait for at least 60 seconds for 0.3.5 and earlier to bootstrapThe basic-min network is still a bit unstable, but only for 0.3.5. (And it's much more unrealiable on macOS than Linux.)
It seems like 0.3.5 needs around 60 seconds to bootstrap and sync descriptors. Later versions have microdescriptor ...The basic-min network is still a bit unstable, but only for 0.3.5. (And it's much more unrealiable on macOS than Linux.)
It seems like 0.3.5 needs around 60 seconds to bootstrap and sync descriptors. Later versions have microdescriptor download fixes, and they can bootstrap and verify in just over 20 seconds on basic-min.
So let's make the minimum wait time 70 seconds (3 consensuses), if any nodes in the network are running 0.3.5 (or earlier).Sponsor 55: Improving the Tor network’s IPv6 supportteorteorhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/23478v3 single onion services appear to be broken2020-06-27T13:18:48Zteorv3 single onion services appear to be brokenYou'll need the latest chutney and the tor branch from legacy/trac#22437 to get these results:
```
PASS: basic-min
PASS: bridges-min
PASS: hs-v2-min
PASS: hs-v3-min
FAIL: single-onion-v23
PASS: bridges+ipv6-min
PASS: ipv6-exit-min
PASS: ...You'll need the latest chutney and the tor branch from legacy/trac#22437 to get these results:
```
PASS: basic-min
PASS: bridges-min
PASS: hs-v2-min
PASS: hs-v3-min
FAIL: single-onion-v23
PASS: bridges+ipv6-min
PASS: ipv6-exit-min
PASS: hs-v23-ipv6
FAIL: single-onion-v23-ipv6
PASS: mixed+hs-v23
```Tor: 0.3.2.x-finalhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/30154Use the built-in unittest module for chutney's unit tests2021-09-16T14:47:51ZteorUse the built-in unittest module for chutney's unit testsFollow-up to legacy/trac#30063.Follow-up to legacy/trac#30063.https://gitlab.torproject.org/tpo/core/chutney/-/issues/40012Use string, not repr, for log reporting PosixPath2020-09-14T15:56:57ZcUse string, not repr, for log reporting PosixPathFix for #40002 introduced a small formatting issue in Chutney's log output, e.g.:
```
NOTE: creating PosixPath('/home/c/git/tor/../chutney/net/nodes.1596403717'), linking to PosixPath('/home/c/git/tor/../chutney/net/nodes')
```
Easy en...Fix for #40002 introduced a small formatting issue in Chutney's log output, e.g.:
```
NOTE: creating PosixPath('/home/c/git/tor/../chutney/net/nodes.1596403717'), linking to PosixPath('/home/c/git/tor/../chutney/net/nodes')
```
Easy enough fix, I just need to make log output refer to the string expression of `PosixPath`s rather than the representation.Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/20513Use public tor network directory authority options in chutney2020-07-23T20:27:24ZteorUse public tor network directory authority options in chutneyChutney currently runs authorities with most options at their defaults.
But the directory authorities on the public tor network run with a set of standard options.
It would be great to use those options as much as possible in chutney (o...Chutney currently runs authorities with most options at their defaults.
But the directory authorities on the public tor network run with a set of standard options.
It would be great to use those options as much as possible in chutney (or even run most networks with them on, and one with them off), so that we are actually testing the code that is running on the real authorities.
For example, when legacy/trac#18319 is implemented, the directory authorities will set AuthDirPinKeys 1 (the default is 0).https://gitlab.torproject.org/tpo/core/chutney/-/issues/14332Use new string formatting interface2020-07-23T20:09:01ZcypherpunksUse new string formatting interfaceThe Python documentation mentions issues with printf-style string formatting and recommends the new `str.format()` interface [0]. The new interface is used in some parts but not everywhere. The attached patch fixes this by using the new ...The Python documentation mentions issues with printf-style string formatting and recommends the new `str.format()` interface [0]. The new interface is used in some parts but not everywhere. The attached patch fixes this by using the new interface where printf-style is currently used.
Additionally, it solves several bugs in `lib/chutney/TorNet.py` caused by the printf-style separator (%) being outside of the `print()`. The bugs result in Chutney crashing when `tor` or `tor-gencert` is not in `PATH` and not specified through the environment variables.
[0] https://docs.python.org/3/library/stdtypes.html#printf-style-string-formattinghttps://gitlab.torproject.org/tpo/core/chutney/-/issues/21563Use bash rather than the default shell2020-06-27T13:18:52ZteorUse bash rather than the default shellUsing the default shell caused issues for a similar tor script - see legacy/trac#21562 for details.Using the default shell caused issues for a similar tor script - see legacy/trac#21562 for details.teorteorhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/29762Update the README for new features2020-06-27T13:18:41ZteorUpdate the README for new featuresWe've added a few new features to chutney recently, so we should update the README. (And keep it up to date when we make future changes.)We've added a few new features to chutney recently, so we should update the README. (And keep it up to date when we make future changes.)teorteorhttps://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 supportteorteorhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/14315Update README2020-06-27T13:19:04ZcypherpunksUpdate READMECurrently the README states that Python 2.5 or later is supported. Chutney already uses features that are present in Python 2.6 and later and Python 2.6 is not maintained.
Should Python 2.7 not be the minimum version?Currently the README states that Python 2.5 or later is supported. Chutney already uses features that are present in Python 2.6 and later and Python 2.6 is not maintained.
Should Python 2.7 not be the minimum version?Nick MathewsonNick Mathewsonhttps://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/30059Update chutney's README2020-06-27T13:18:41ZteorUpdate chutney's READMEIn legacy/trac#29729, I discovered some missing information in Chutney's README.In legacy/trac#29729, I discovered some missing information in Chutney's README.teorteorhttps://gitlab.torproject.org/tpo/core/chutney/-/issues/10136Unknown options in torrc file2020-06-27T13:19:07ZTracUnknown options in torrc fileI am new(student) to tor. When I try to run chutney => ./chutney start networks/basic , it is not able to run the tor. When I looked at the torrc file generated and tried running them separately, I got the following warnings:
* Unknown ...I am new(student) to tor. When I try to run chutney => ./chutney start networks/basic , it is not able to run the tor. When I looked at the torrc file generated and tried running them separately, I got the following warnings:
* Unknown option 'TestingClientDownloadSchedule'
* Unknown option 'TestingV3AuthVotingStartOffset'
with this I also got(after commenting above lines from torrc file) :
* TestingV3AuthInitialVoteDelay is way too low
**Trac**:
**Username**: vikassyNick MathewsonNick Mathewson