mirrors/arti.git/tests/chutney/integration-e2e, branch arti-v1.6.0 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.6.0 2025-09-29T16:22:19Z chutney CI: move benchmark from e2e script to `test` script 2025-09-29T16:22:19Z Jim Newsome jnewsome@torproject.org 2025-09-08T19:43:53Z urn:sha1:b33e821c8771ac3ef4cf4378f9af04c259fc3e2a chutney ci: move "chutney bootstrap" from `setup` to `bootstrap` 2025-09-29T16:22:19Z Jim Newsome jnewsome@torproject.org 2025-09-05T00:08:05Z urn:sha1:ca53c6dc248023cbf6350c1c5cc71a8e08c2ccc6 This makes the `setup` script a bit more clearly single-purpose of resolving and storing the configuration, without actually acting on it yet. integration-e2e: ensure chutney network teardown on exit 2025-06-05T16:14:12Z Jim Newsome jnewsome@torproject.org 2025-05-27T23:17:23Z urn:sha1:4305dcd2758f3e3dc642a0504dba2c59bac55156 chutney CI: Remove no-op PROXY module 2025-06-05T16:14:12Z Jim Newsome jnewsome@torproject.org 2025-05-21T23:31:25Z urn:sha1:4be766ae64d31274d375719ec619cca3afa5cc2b An arti proxy is already started as part of the chutney network. chutney test: remove extra arti process 2025-06-05T16:14:12Z Jim Newsome jnewsome@torproject.org 2025-05-21T22:54:50Z urn:sha1:9e8dfb58ab25f84e1d803cd07ef4924000dc7c1a chutney CI: get tor client port for arti-bench more robustly 2025-06-05T16:14:12Z Jim Newsome jnewsome@torproject.org 2025-05-21T18:29:03Z urn:sha1:1929703f514fe5b64be2b77b2c88a5737c616b27 Use the new exported json metadata to get a tor client port instead of hard-coding it. CI: bump chutney commit 2025-06-05T16:14:12Z Jim Newsome jnewsome@torproject.org 2025-05-19T21:18:25Z urn:sha1:780cf50ebd51f6ad099ca2bebd282ae6a9f904e5 Also update the hard-coded tor client port here to match updates to the chutney network. Replace CHUTNEY_PATH with CHUTNEY_BIN 2024-11-06T15:47:34Z Jim Newsome jnewsome@torproject.org 2024-10-30T19:40:06Z urn:sha1:31dcc20d06df620475a1b393a5b34d5987a35030 We no longer need a path to a checkout of the chutney repository; we just need the chutney binary itself. We still allow this to be set explicitly with CHUTNEY_BIN, but fall back to finding it on the PATH. chutney test: reference network as built-in instead of full path 2024-11-06T15:47:34Z Jim Newsome jnewsome@torproject.org 2024-10-30T18:27:01Z urn:sha1:7c250304099bd1dda8783a75e0aab11b56a16394 This takes advantage of a feature added in https://gitlab.torproject.org/tpo/core/chutney/-/merge_requests/31. This is a step towards not needing to set CHUTNEY_PATH to point to a chutney repository. chutney test: rework installation and tracking of chutney itself 2024-09-18T18:26:07Z Jim Newsome jnewsome@torproject.org 2024-09-17T15:51:06Z urn:sha1:2ca52e2cc246efd77ab96b85262edc2b3afc23aa Previously `tests/chutney/setup` would locate *or install* chutney and set `CHUTNEY_PATH` for itself. However that `CHUTNEY_PATH` wasn't propagated to other steps or "up" to the new `integration-e2e` wrapper script. Tracking it in the arti.run along with other dynamic info lets us ensure we consistently use the same chutney across steps, and in the higher level `integration-e2e` script.