test(testnet): clarify directed runtime latency syntax

This commit is contained in:
Nicholas Dudfield
2026-06-23 16:19:10 +07:00
parent 38f4d53ebf
commit 8e542c32e0
2 changed files with 19 additions and 14 deletions

View File

@@ -57,8 +57,8 @@ tests:
network:
rc:
- rng_poll_ms=250
- n0@n2:delay=750,jitter=100,msg=proposal
- n2@n0:delay=750,jitter=100,msg=proposal
- n0->n2:delay=750,jitter=100,msg=proposal
- n2->n0:delay=750,jitter=100,msg=proposal
- name: latency_slow_minority_export
script: .testnet/scenarios/perf/ce_export_latency_probe.py
@@ -70,18 +70,18 @@ tests:
network:
rc:
- rng_poll_ms=250
- n3@n0:delay=500,jitter=100,msg=proposal
- n3@n1:delay=500,jitter=100,msg=proposal
- n3@n2:delay=500,jitter=100,msg=proposal
- n4@n0:delay=500,jitter=100,msg=proposal
- n4@n1:delay=500,jitter=100,msg=proposal
- n4@n2:delay=500,jitter=100,msg=proposal
- n0@n3:delay=500,jitter=100,msg=proposal
- n1@n3:delay=500,jitter=100,msg=proposal
- n2@n3:delay=500,jitter=100,msg=proposal
- n0@n4:delay=500,jitter=100,msg=proposal
- n1@n4:delay=500,jitter=100,msg=proposal
- n2@n4:delay=500,jitter=100,msg=proposal
- n3->n0:delay=500,jitter=100,msg=proposal
- n3->n1:delay=500,jitter=100,msg=proposal
- n3->n2:delay=500,jitter=100,msg=proposal
- n4->n0:delay=500,jitter=100,msg=proposal
- n4->n1:delay=500,jitter=100,msg=proposal
- n4->n2:delay=500,jitter=100,msg=proposal
- n0->n3:delay=500,jitter=100,msg=proposal
- n1->n3:delay=500,jitter=100,msg=proposal
- n2->n3:delay=500,jitter=100,msg=proposal
- n0->n4:delay=500,jitter=100,msg=proposal
- n1->n4:delay=500,jitter=100,msg=proposal
- n2->n4:delay=500,jitter=100,msg=proposal
- name: latency_export_no_veto_with_delay
script: .testnet/scenarios/export/export_no_veto_missing_observation.py

View File

@@ -116,6 +116,11 @@ struct ConsensusTestConfig
- "peer_defaults" — default send fault config for all peers
- "peer:ip:port" — per-peer send fault override
Peer keys match the outbound PeerImp remote endpoint used at send time.
In x-testnet, n0->n2 resolves to peer:127.0.0.1:<n2 peer port> and affects
only node 0's outbound sends to node 2. Reverse traffic and inbound
ephemeral endpoints are separate unless configured separately.
RPC handler: runtime_config (Role::ADMIN)
Disconnect handler: disconnect (Role::ADMIN)