"over max translation" appears in the log before the trace, but we're
checking for the trace immediately after waiting.  This changes the test
to wait for "packet is dropped" instead, which appears at the end of the
trace.  This created a race and occasional test failures.

CC: William Tu <u9012...@gmail.com>
Fixes: d1ea2cc3de99 ("xlate: auto ofproto trace when recursion too deep")
Signed-off-by: Ben Pfaff <b...@ovn.org>
---
I noticed this only after I committed the previous patch, sorry about that!

 tests/ofproto-dpif.at | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/ofproto-dpif.at b/tests/ofproto-dpif.at
index fd78c5d9b593..48cbc672d204 100644
--- a/tests/ofproto-dpif.at
+++ b/tests/ofproto-dpif.at
@@ -8487,7 +8487,7 @@ AT_CHECK([ovs-ofctl add-flows br0 flows])
 
 AT_CHECK([ovs-appctl netdev-dummy/receive br0 
'in_port(1),eth(src=50:54:00:00:00:09,dst=50:54:00:00:00:0a),eth_type(0x1234)'],
 [0], [stdout])
 
-OVS_WAIT_UNTIL([grep 'over max translation' ovs-vswitchd.log])
+OVS_WAIT_UNTIL([grep 'packet is dropped' ovs-vswitchd.log])
 
 dnl make sure the full ofproto trace dump is present
 AT_CHECK([grep -c "^ *resubmit" ovs-vswitchd.log],
-- 
2.16.1

_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to