| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Since we're validating the presence of jq, we might as well handle it
consistently with the other dependencies and provide a way to specify
where it is.
|
| |
|
|
|
|
| |
This wasn't a pre-existing environment variable, and now it can be set
via command-line if it needs to be overridden. I don't see much reason
to use an environment variable here.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
It made sense to have this as part of the setup when the chutney network
itself didn't include arti; i.e. this used to be just validating the
non-chutney tor network before adding chutney nodes.
Now that the chutney network natively includes arti nodes, `chutney
verify` is testing those nodes; i.e., testing arti.
|
| | |
|
| | |
|
| |
|
|
|
| |
This is a wrapper script for running `tests/chutney/integration-e2e`
under shadow.
|
| | |
|
| |
|
|
|
|
| |
It looks like it changed at some point. Rather than hard-coding,
just do the lookup locally and compare the tor-lookup result against
that.
|
| |
|
|
|
|
|
|
|
|
| |
This commit changes the shebang in all shell scripts from absolute
paths (such as `/bin/bash` or `/usr/bin/python3`) to the `/usr/bin/env`
binary with the accompanying interpreter as it's argument.
The reason for this are as follows:
- NixOS cannot work with absolute paths
- BSD systems install their packages in /usr/local/bin
|
| | |
|
| |
|
|
|
| |
Apparently 5353 is commonly used for mDNS, and so counts as "already in
use" on many consumer machines.
|
| | |
|
| |
|
