| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
This keeps everything together and avoids clobbering previous artifacts,
since chutney already creates a unique nodes dir in every run.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This organizes the code a bit better and gives nicer output. It also
separates individual test cases and subcases, continuing to try to
complete other tests when one fails instead of exiting.
|
| |
|
|
|
|
|
| |
chutney replaced Node.socksport (a single optional port) with
Node.socksport_endpoints (a sequence of bound addresses and ports).
Update for compatibility, and test all of the exposed endpoints where
relevant.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
* Gets rid of shelling out to jq. We could also accomplish that with the
json module, but this way also gives us:
* Better error detection and handling. In particular this lets mypy
statically detect trying to access fields of the wrong name or type.
It will also make it easier to bump to the latest chutney, which has
replaced `socksport` with `socksport_endpoints`, which would be more
difficult to work with as json, especially via `jq`.
|
| | |
|
| | |
|
| |
|
|
| |
Bump chutney, and migrate to CLI changes introduced in chutney!101
|
| |
|
|
| |
Also search several candidate paths.
|
| |
|
|
|
|
| |
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.
|
| | |
|
| |
|