summaryrefslogtreecommitdiff
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* shadow ci: Set stop time to 30m instead of 27mJim Newsome2022-10-141-4/+1
| | | | | This was a temporary stop-gap to work around a busy loop that seemed to happen before. I am no longer able to reproduce any such problem.
* Create a shadow-based integration testJim Newsome2022-10-0552-0/+544
| | | | Fixes https://gitlab.torproject.org/tpo/core/arti/-/issues/174
* test/chutney/setup: Set allow_running_as_root as needed.Nick Mathewson2022-08-241-1/+9
|
* add default chutney path to arti-bench scripttrinity-1686a2022-05-261-3/+11
|
* make almost all scripts use bash and set euo pipefailtrinity-1686a2022-05-253-5/+7
|
* chutney/teardown: validate that pid is setJim Newsome2022-05-231-1/+1
|
* chutney test stop network when arti died or did not starttrinity-1686a2022-05-052-15/+15
|
* Use port 35353 for testing, not 5353.Nick Mathewson2022-03-152-3/+3
| | | | | Apparently 5353 is commonly used for mDNS, and so counts as "already in use" on many consumer machines.
* comment AAAA test and explain why it's disabledtrinity-1686a2022-03-141-1/+4
|
* add simple unit test on UDPtrinity-1686a2022-03-141-1/+1
|
* add integration test and fill semver_statustrinity-1686a2022-03-142-1/+7
|
* tests/chutney/setup: Transfer changes from just-deleted codeIan Jackson2022-03-111-3/+3
| | | | | | | It turns out that the clone-and-hack in tests/chutney/arti-bench was not identical to the original in tests/chutney/setup. I diffed the two and preferred the version from arti-bench.
* tests/chutney: Merge chutney-launching scriptsNick Mathewson2022-03-102-28/+53
| | | | | | | | | Formerly, the "launch a chutney network" code was duplicated in "setup" and "arti-bench", since "setup" always launched an arti proxy, while "arti-bench" didn't want that functionality. Now the "setup" script launches an arti proxy conditionally, depending on whether the "proxy" argument is given.
* chutney/setup: Wait for port 9150 to open after launching artiNick Mathewson2022-02-281-1/+15
| | | | | This is not a replacement for a real startup protocol, but it may help repair our CI.
* tests/chutney/setup: Reduce sleepIan Jackson2022-02-181-1/+3
| | | | Now that arti listens immediately, a very short sleep ought to do.
* rename *.sh scripts to bare nameIan Jackson2022-02-184-1/+1
| | | | | | | | | As per #309 Update all references. There is one remaining hit for git-grep '\.sh\b' namely "build.sh" in maint/reproducible_build, which I think is the build script for osxcross - ie, an external project.
* arti-bench: run the benchmarks in CI, and keep the resultseta2022-02-031-0/+16
| | | | | This adds `arti-bench` to the `integration` job in the CI pipelines, and keeps around the JSON benchmark output for later comparison.
* Fix/suppress shellcheck errors in teardown.shNick Mathewson2022-01-271-0/+14
| | | | Rationale: It's good to have all of our scripts pass shellcheck.
* arti-bench.sh: Handle the case where CHUTNEY_PATH is set.Nick Mathewson2021-12-211-8/+32
| | | | | 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.Nick Mathewson2021-12-211-0/+5
| | | | (An empty $RUST_LOG no output, and confuse the nickm^Wuser.)
* tests/chutney/setup.sh: Fix a shellcheck warning.Nick Mathewson2021-12-212-2/+4
| | | | | shellcheck doesn't like `export FOO="$(bar)"` as one line, since it has the possibility of missing errors.
* Introduce an experimental benchmarking utility for Artieta2021-12-161-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 Mathewson2021-12-052-6/+11
| | | | This is per a suggestion from @trinity-1686a.
* When tearing down test net, always tear down test net :)Nick Mathewson2021-12-021-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 Mathewson2021-12-022-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 scriptsTrinity Pointard2021-10-283-0/+46
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-26 18:18:20 +0000