mirrors/arti.git/tests/chutney/integration-e2e-shadow, branch main mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=main 2026-07-27T18:51:49Z integration-e2e-shadow: use shadow-exec to forward output to console 2026-07-27T18:51:49Z Jim Newsome jnewsome@torproject.org 2026-07-27T18:16:52Z urn:sha1:d8c16e7632edcf5a803eb7c4ce7a8e2771940a78 integration-e2e-shadow: use shadowtools.config to typecheck generated shadow config 2026-07-27T18:33:40Z Jim Newsome jnewsome@torproject.org 2026-07-27T18:21:25Z urn:sha1:84ffbad4da30eb05a27177298b84d9fbec988ec8 * build shadowtools python package in `build-shadow` job * install the shadowtools python package in python3-checks, so that usage can be checked with mypy. * integration-e2e-shadow: generate typed shadow config integration-e2e-shadow: move artifacts into nodes dir 2026-07-23T20:45:04Z Jim Newsome jnewsome@torproject.org 2026-07-22T19:51:20Z urn:sha1:f30d18718df8f76b2f83c19e0be450bdd0993496 This keeps everything together and avoids clobbering previous artifacts, since chutney already creates a unique nodes dir in every run. integration-e2e-shadow: config and init outside of shadow 2026-07-23T20:45:04Z Jim Newsome jnewsome@torproject.org 2026-07-15T23:10:43Z urn:sha1:9cce71fedfe83ace90ee16503d92762d4fb2add5 This makes the chutney network configuration available *before* we generate the shadow config file, which we need in order to generate multi-host networks. chutney test: split network init from network bootstrap 2026-07-23T20:45:04Z Jim Newsome jnewsome@torproject.org 2026-07-15T22:29:33Z urn:sha1:763ddf58aec173d8ec1414433d580683b6164ca8 This is in preparation to move the init step outside of the shadow simulation in integration-e2e-shadow (while leaving the bootstrap step inside the shadow simulation). integration-e2e-shadow: inline integration-e2e 2026-07-23T20:45:04Z Jim Newsome jnewsome@torproject.org 2026-07-15T22:02:09Z urn:sha1:ab5d58bdbe85efa9f6e015b7350544669b330591 This is in preparation to diverge somewhat. In particular, we want to do some of the configuration and setup from *outside* of shadow, so that we can generate shadow configs that take the chutney network configuration into account. integration-e2e-shadow: add support for subcommands 2026-07-23T20:45:04Z Jim Newsome jnewsome@torproject.org 2026-07-15T21:48:31Z urn:sha1:20e9ecdfb8b30386fafc13197b1642c540cbaf47 integration-e2e-shadow: split out helper _configure_and_run_shadow 2026-07-23T20:45:04Z Jim Newsome jnewsome@torproject.org 2026-07-15T21:44:13Z urn:sha1:3cf9c785d0939bd457a804c1d31382745d7fbad5 integration-chutney-shadow: disable shadow spin-looping 2026-04-21T17:55:38Z Jim Newsome jnewsome@torproject.org 2026-04-21T17:55:38Z urn:sha1:ca6c5d85e93b991bd3bae8d6debe473e3ddba142 shadow's default behavior of spin-looping is bad behavior in a shared environment. This is already disabled in integration-shadow. CI: Disble shadow cpu-pinning 2026-04-21T17:51:48Z Jim Newsome jnewsome@torproject.org 2026-04-21T17:51:48Z urn:sha1:1b3337730e4f87100b46521b211a7a6a2c7cc506 In CI, shadow's default behavior of pinning to CPU cores can result in multiple instances of shadow fighting over the same CPU cores instead of using idle ones.