mirrors/arti.git/tests, branch arti-v2.5.1

integration-e2e-shadow: use shadow-exec to forward output to console

2026-07-27T18:51:49Z

integration-e2e-shadow: use shadowtools.config to typecheck generated shadow config

2026-07-27T18:33:40Z

* 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: change default data-dir to TOPLEVEL/chutney-net

2026-07-23T20:45:04Z

integration-e2e-shadow: move artifacts into nodes dir

2026-07-23T20:45:04Z

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

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

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

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

integration-e2e-shadow: split out helper _configure_and_run_shadow

2026-07-23T20:45:04Z

chutney test network: add 4 suitable middle/guard/vg relays

2026-06-16T04:06:03Z

With the chutney bump in the previous commit alone, we hit arti#2463 consistently. According to the spec, a hidden service using vanguards-lite needs 2 guards and 4 vanguards . All 6 of those relays need to be Fast and Stable. At least the 2 guards also need to be Measured. (Probably the 4 vanguards too, but I haven't verified). authority relays are never considered Measured. Prior to the chutney bump, none of the relays were, but since chutney!142, we create a bandwidth file to ensure the non-authorities *are* Measured, and will get the Fast flag. (IIUC, tor doesn't apply the bandwidth measurements to authorities). Maybe the presence of *some* measured relays gets us out of some fallback path that was getting used before to allow unmeasured relays? Adding the additional relays seems to fix the issue.