mirrors/arti.git/tests/chutney, branch arti-v0.0.3mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.0.32021-12-21T14:54:16Zarti-bench.sh: Handle the case where CHUTNEY_PATH is set.2021-12-21T14:54:16ZNick Mathewsonnickm@torproject.org2021-12-21T14:53:13Zurn:sha1:032b0d2575cfdabc0cfafb164968808372f5f082
Previously, this case would cause arti-bench to hang forever, trying
to bootstrap against one network while another network was running.
arti-bench.sh: set $RUST_LOG if it isn't set.2021-12-21T14:54:16ZNick Mathewsonnickm@torproject.org2021-12-21T14:35:21Zurn:sha1:ba6828d9fe49565eaca433e9a40d296c72fda43e
(An empty $RUST_LOG no output, and confuse the nickm^Wuser.)
tests/chutney/setup.sh: Fix a shellcheck warning.2021-12-21T14:54:16ZNick Mathewsonnickm@torproject.org2021-12-21T14:50:59Zurn:sha1:584e46d6194e4b3cd9d830258404db81fdb9dc5e
shellcheck doesn't like `export FOO="$(bar)"` as one line, since it
has the possibility of missing errors.
Introduce an experimental benchmarking utility for Arti2021-12-16T16:12:59Zetator@eta.st2021-12-14T17:29:04Zurn:sha1:06a94288caa6cdb61d90982f171b7da688951b6b
The new `arti-bench` crate does a simple end-to-end benchmark test
embedding Arti: it generates some random data (of configurable amount,
depending on command-line parameters), and then sends said data back and
forth via Arti (which should be configured to use a local Chutney
network).
Additionally, the benchmark can also be run via a local SOCKS5 server
(in order to benchmark the performance via a local Chutney node, for
comparison).
The `tests/chutney/arti-bench.sh` sets up and tears down Chutney as
required to make this work.
This is very much a first cut; there are many things that should
eventually get added, such as support for multiple connections, JSON
output capabilities, running multiple tests, ...
chutney: Make $target relative to ${CHUTNEY_PATH}2021-12-05T21:04:46ZNick Mathewsonnickm@torproject.org2021-12-05T20:38:45Zurn:sha1:9f9bb3e4c1e48206590916875a405597f2317c4b
This is per a suggestion from @trinity-1686a.
When tearing down test net, always tear down test net :)2021-12-02T14:25:28ZNick Mathewsonnickm@torproject.org2021-12-02T14:25:28Zurn:sha1:b009e31410fb7b5c09662059011f5e967ad88d84
Previously, if the arti process had died or been killed, we wouldn't
reach the point where we called "chutney stop".
Detect and use CHUTNEY_PATH in test scripts.2021-12-02T14:22:52ZNick Mathewsonnickm@torproject.org2021-12-02T14:22:52Zurn:sha1:ec2245164f741075881c5ce9a03b7f9dc7247fcb
If the user has CHUTNEY_PATH set, respect that value, rather than
cloning a local chutney.
Also, if we have a local chutney, then update it in case there have
been changes.
move integration tests to scripts2021-10-28T15:28:22ZTrinity Pointardtrinity.pointard@gmail.com2021-09-28T17:36:00Zurn:sha1:0438a3da93ce8d0e805bf1903761441621f28e0c