| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | Introduce an experimental benchmarking utility for Arti | eta | 2021-12-16 | 1 | -0/+14 | |
| | | | | | | | | | | | | | | | | | | | | 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} | Nick Mathewson | 2021-12-05 | 2 | -6/+11 | |
| | | | | | This is per a suggestion from @trinity-1686a. | |||||
| * | When tearing down test net, always tear down test net :) | Nick Mathewson | 2021-12-02 | 1 | -1/+3 | |
| | | | | | | 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. | Nick Mathewson | 2021-12-02 | 2 | -9/+29 | |
| | | | | | | | | | 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 scripts | Trinity Pointard | 2021-10-28 | 3 | -0/+46 | |
 |
index : mirrors/arti.git | |
| mirror of https://gitlab.torproject.org/tpo/core/arti |
| summaryrefslogtreecommitdiff |