On 1/30/26 11:43 AM, [email protected] wrote: >>> +# UDP nc with "-k" is bit tricky to cleanup, especially on test >>> failures, due to its >>> +# child processes keeping the listening port open. If they are not >>> cleaned up properly, >>> +# the whole test cleanup hangs. >> Is this something we need to fix in other tests too? Outside of this >> patch I mean. > I briefly looked and I didn't find any other tests that would use `nc` > "udp server" with the option `-k`. So it doesn't seem like we need to > add this to any other test. > > Usually you can get away without using the '-k' if you want to test > just a single connection, or if you can re-use source port on the > client side for multiple "connections". > However in this tests, the "server" gets probed repeatedly by the > controller's service check. Without the '-k' option, only the first > probe would show success, and following probes would fail.
Hmm, I was going to ask how we test UDP health checks for non-router-IPs but It seems we don't. :) OK, thanks for digging into this, it makes sense for your feature test, so let's keep it as is. Thanks, Dumitru _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
