It seems to me that depending on test machine load or other scheduling reasons, it is possible that some tests fail sometimes, even if there is no real failure. One such case below, where it seems that the middle reply comes in a bit later than anticipated. On repeat this failure did not occur again.
>From testsuite.log: ./ofproto.at:1470: sed 's/ (xid=0x[1-9a-fA-F][0-9a-fA-F]*)//' monitor.log --- - 2012-12-04 16:26:11.275437104 +0200 +++ /home/rajahalm/openvswitch/tests/testsuite.dir/at-groups/543/stdout 2012-12-04 16:26:11.000000000 +0200 @@ -1,8 +1,8 @@ NXST_FLOW_MONITOR reply (xid=0x0): event=ADDED table=0 cookie=0 in_port=1 actions=output:2 +send: OFPT_FLOW_MOD: DEL priority=0 actions=drop NXST_FLOW_MONITOR reply (xid=0x0): event=ADDED table=0 cookie=0 in_port=2 actions=output:1 -send: OFPT_FLOW_MOD: DEL priority=0 actions=drop NXST_FLOW_MONITOR reply (xid=0x0): event=ABBREV xid=0x12345678 OFPT_BARRIER_REPLY: The test is: # Check that our own changes are reported as abbreviations. ovs-appctl -t ovs-ofctl ofctl/set-output-file monitor.log ovs-ofctl add-flow br0 in_port=1,actions=output:2 ovs-ofctl add-flow br0 in_port=2,actions=output:1 ovs-appctl -t ovs-ofctl ofctl/send 010e004812345678003fffff00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000ffffffffffff0000 ovs-appctl -t ovs-ofctl ofctl/barrier AT_CHECK([ovs-ofctl dump-flows br0 | ofctl_strip], [0], [NXST_FLOW reply: ]) AT_CHECK([sed 's/ (xid=0x[[1-9a-fA-F]][[0-9a-fA-F]]*)//' monitor.log], [0], [NXST_FLOW_MONITOR reply (xid=0x0): event=ADDED table=0 cookie=0 in_port=1 actions=output:2 NXST_FLOW_MONITOR reply (xid=0x0): event=ADDED table=0 cookie=0 in_port=2 actions=output:1 send: OFPT_FLOW_MOD: DEL priority=0 actions=drop NXST_FLOW_MONITOR reply (xid=0x0): event=ABBREV xid=0x12345678 OFPT_BARRIER_REPLY: ]) _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
