test(e2e): assert the §E.2 idle-silence window in every kernel scenario

The L2-anchor spec's behavioral guarantee — an idle link stays silent for
5 s once the enslavement burst settles — only ran in the Dynamips and
Docker suites. It now also runs in QEMU, IOU, the IOL container, the
switch fast path and the switch cascade, which covers every host-device
creation path:

* tap create (Dynamips/QEMU/IOU anchors), docker create_veth (Docker host
  ends; the cascade's race-loser end is hardened after create by the
  server), bridge add_nio_tap (the IOL container anchor, the fifth
  creator), and the brctl switch bridges, whose multicast snooping is off
  precisely so the bridge role can reach silence;
* each scenario silences its guests first (IOS interfaces shut through
  the console; Docker guests' links down) and re-verifies the ping after;
* the cascade measures 8 devices at once (four absorbed router anchors,
  both cascade ends, both switch bridges).

IOL 158 s, cascade 293 s, ESW fast path 378 s, QEMU 428 s, IOU 308 s —
all green.
This commit is contained in:
YueGuobin committed 2026-10-06 00:21:10 +08:00
1 parent 1f544c96a5
commit ff41a54364
11 files changed
+166 -16

No files matched your search

+4 -3
View File
@@ -141,9 +141,10 @@ expected), no kernel bridge holding the tap.
The repo suite `tests/e2e/test_qemu_kernel_datapath.py` covers the same
ground with a *real* guest: two IOSv routers (a real qcow2 image, linked
clone, the real IOS CLI on the telnet console) — the full kernel lifecycle
(anchors at start, per-link bridge membership, pure-L2 anchors, real ICMP,
netem delay, suspend, capture, link delete/re-create, node stop/start
rewiring, zero residue on project delete) plus the relay negative control,
(anchors at start, per-link bridge membership, pure-L2 anchors, the §E.2
idle-silence window with the guests shut, real ICMP, netem delay, suspend,
capture, link delete/re-create, node stop/start rewiring, zero residue on
project delete) plus the relay negative control,
where the anchor is up and carrying as the relay's AF_PACKET endpoint (QEMU
has no other leg — the TAP is the netdev on the relay too). It needs an L3
IOSv image in the images directory's `QEMU` subfolder; a raw node must also