teor2345 / chutney Public
forked from torproject/chutneyno-zombies
Commits on May 2, 2017
-
Disable DNS via chutney exits by default
This makes chutney much more reliable, and removes the dependency on an external DNS resolver. This is a breaking change for those who run DNS-based queries through chutney. To restore DNS support, use: CHUTNEY_DNS_CONF="/etc/resolv.conf" Closes ticket #21903, and other related tickets.
-
Make all chutney tors exit when tools/test-network.sh exits
Fixes #20409, as long as chutney and tools/test-network.sh do not hang. (Hangs shouldn't happen, if they do, it's a separate bug.)
-
-
Fix an inconsistent echo call in tools/test-network.sh
No behaviour change
-
Make tor clean up connections before stopping a chutney network
This increases integration test coverage, and improves the reliability of any statistics being gathered on chutney networks. Implements feature #21901.
Commits on Mar 1, 2017
-
-
And fix some bash-isms. This restores support for BSDs without bash installed. Reverts 0d57f92. Closes 21575.
Commits on Feb 27, 2017
-
Make the formatting of warnings slightly more consistent
Part of tor's 21570.
-
Reserve an exit status of 2 for "unknown command-line argument"
Required for tor's 21570 to work.
-
If there are warnings, always echo the canonical nodes path
Revision of 21571 to better suit tor's needs in 21570.
-
Add a warning-only mode to test-network.sh
And provide a canonical path to the nodes directory in warnings.sh. This is part of tor feature 21570. Closes 21572.
-
Add a quiet mode to test-network.sh and warnings.sh
This prepares for the tor changes in 21570. Closes 21571.
-
-
Make a unique directory each chutney run, and symlink to a standard name
Instead of moving the directory to a unique path at the start of the next run, which makes it impossible to find if running several networks in succession, like we do in 'make test-network-all'. Closes 21567.
-
Handle CHUTNEY_DATA_DIR correctly, even if it's relative
And handle it consistently across chutney and scripts. Closes 21568.
-
-
Make chutney accept relative paths, as well as the scripts
Closes 21467 (finally!)
-
When we fail to parse an option, remind the user to update chutney
Partial fix for 20091.
-
Use bash rather than the default shell
Closes #21563, related to tor's #21562.
-
Check that relative paths actually have what we need in them
If they don't, use the script path. Finally fixes #21521, I hope!
-
Change the default mode when creating directories
Every call to `mkdir_p` uses mode 448 which is a sensible default. Using this mode as the global default prevents future problems, removes duplicate comments and simplifies existing calls. Closes #21552.
Commits on Feb 24, 2017
-
Maybe we should fix the configs (or tor) instead? Part of #21371.
-
Refactor and document the warnings.sh code
Add arguments to test-network.sh for warnings Make the enviromental variables strings rather than integers Fixes #21371.
Commits on Feb 23, 2017
-
Make chutney shell scripts support relative paths
Part of #21521. Remaining work: make chutney python code use CHUTNEY_PATH.
-
Handle hidden services on old tor versions in hsaddress.sh
Closes #21533.
-
uniq -c prints counts with variable spacing. We shouldn't carry that through to the output. Closes #21531.
-
Log all warnings generated by tor after testing a network
Part of #21371.