On Wed, Feb 18, 2026 at 12:48 PM Matteo Perin via dev < [email protected]> wrote:
> The "ovs-route - unsupported rules" test routing rule checks were failing > on systems having non-standard routing rules. > > These failures occurred because the test performed exact output matching > on the full output of 'ovs-appctl ovs/route/rule/show', which includes > both user-added and system-cached rules. > > When the system has additional routing rules that meet certain criteria > (FR_ACT_TO_TBL action without unsupported selectors like fwmark, dport, > sport, iif, ipproto, or tun_id), OVS caches them, as expected, causing > them to appear in the "Cached:" section of the output. > > "ovs-route - unsupported rules" was modified in order to take this > situation > into account. It now captures the full initial cache state before adding > test rules and verifies that the cache state remains unchanged after adding > unsupported rules (keeping the intent of the test intact). > > Signed-off-by: Matteo Perin <[email protected]> > > I was going to suggest that you could pipe directly into the target filename. But I see that in the v1 Ilya initially suggested piping to stdout and renaming. So looks good to me! Acked-by: Mike Pattrick <[email protected]> _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
