ffff4ed676
The LCM bridge carrier reflects whether its container-side port is live. Split execution can inspect it before the LCM suite tears that state down, so the bridge can appear either live or without carrier. Carrier state is not the route line's only variable part: ip route also emits a trailing separator. Account for that separator after the optional linkdown flag so both carrier states match. Accept both observed route and link forms in every board's copy of the affected expectations while keeping every address, interface attribute, and the carrier-to-state pairing constrained. Assisted-by: codex:gpt-5 Assisted-by: claude:opus-5:orchestrator Assisted-by: codex:gpt-5.6-sol:medium-fast References: CI-7 Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org> |
||
|---|---|---|
| .. | ||
| acceleration-plan-components | ||
| 005-build-config.t | ||
| 010-network.t | ||
| 011-tls.t | ||
| 020-ubus.t | ||
| 030-wifi.t | ||
| 100-prplmesh.t | ||