mirrors/arti.git/tests/chutney, branch arti-v1.6.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.6.02025-09-29T16:22:19Zchutney ci setup: encapsulate config as a whole2025-09-29T16:22:19ZJim Newsomejnewsome@torproject.org2025-09-10T20:43:39Zurn:sha1:7f1aca9466a91f825d4cffb9942686556d598355
This is partly just to get more code out of "main", but also paves the
way a bit for reusing this config code in the `integration-e2e-shadow`
wrapper script, to support the same command-line arguments there.
chutney CI: store and use jq path2025-09-29T16:22:19ZJim Newsomejnewsome@torproject.org2025-09-10T20:02:49Zurn:sha1:df531a543d240e1a765c65651b7cabf1a082b04b
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.
chutney setup: refactor config options into Resolver objects2025-09-29T16:22:19ZJim Newsomejnewsome@torproject.org2025-09-09T20:08:14Zurn:sha1:e4048fa45d2182e1dafc8e0fc52a1396b309e7b6
Encapsulate the logic of finding and validating each option into their
own objects (e.g. so that specification of corresponding command-line
option goes together with other related logic).
chutney ci: remove CHUTNEY_BIN env variable2025-09-29T16:22:19ZJim Newsomejnewsome@torproject.org2025-09-09T18:12:11Zurn:sha1:353e79c5d65547135a8de71edfe50954f6f6b4b0
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.
chutney ci setup: allow bin locations to be set by cmd line2025-09-29T16:22:19ZJim Newsomejnewsome@torproject.org2025-09-08T21:48:49Zurn:sha1:2fc43f22e7c7b7aece13986785c3a621129edac8chutney setup: break into functions2025-09-29T16:22:19ZJim Newsomejnewsome@torproject.org2025-09-08T21:19:58Zurn:sha1:5e07619bbf2bd6b71bd3c128b062a8074b7a1c87chutney ci: rewrite setup script in python2025-09-29T16:22:19ZJim Newsomejnewsome@torproject.org2025-09-08T20:59:12Zurn:sha1:8db8f01f6dd2fe8d46affa87bf66fa2eaf6b8238
We avoid much refactoring at this step to minimize functional changes
from the shell script.
chutney CI: move benchmark from e2e script to `test` script2025-09-29T16:22:19ZJim Newsomejnewsome@torproject.org2025-09-08T19:43:53Zurn:sha1:b33e821c8771ac3ef4cf4378f9af04c259fc3e2achutney ci: move "chutney bootstrap" from `setup` to `bootstrap`2025-09-29T16:22:19ZJim Newsomejnewsome@torproject.org2025-09-05T00:08:05Zurn: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.
chutney ci: move "chutney verify" test from `setup` to `test`2025-09-29T16:22:19ZJim Newsomejnewsome@torproject.org2025-09-04T23:58:54Zurn:sha1:85328d9baf8fabf7a3c12ead0e92190098962285
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.