On 20 March 2017 at 14:21, Ben Pfaff <[email protected]> wrote: > On Mon, Mar 20, 2017 at 02:15:24PM -0700, Joe Stringer wrote: >> On 9 March 2017 at 03:49, nickcooper-zhangtonghao <[email protected]> >> wrote: >> > +ovs-appctl time/warp 1000 >> > +AT_CHECK([ovs-appctl netdev-dummy/receive br0 \ >> > + >> > '01005E010101000C29A027D18100000108004500001C000100004002CBCBAC102201E00101011114EEEB00000000']) >> > + >> > +OVS_WAIT_UNTIL([ovs-appctl fdb/show br0 | grep '00:0c:29:a0:27:d1']) >> > +OVS_WAIT_UNTIL([ovs-appctl fdb/show br1 | grep '00:0c:29:a0:27:d1']) >> > +OVS_WAIT_UNTIL([ovs-appctl fdb/show br2 | grep '00:0c:29:a0:27:d1']) >> > + >> > +OVS_WAIT_UNTIL([ovs-appctl mdb/show br0 | grep 'querier']) >> >> Hmm, on my system this test just times out on this line and I get the >> dreaded 'hard failure' (ie, it tried several times and the condition >> never became true). >> >> (My system is a bit weird, with newer kernel, python3 by default and >> other things, but I don't see how any of that relates to this >> particular problem..) > > As a minor point here, I can at least confirm that I did run the tests > before applying them and that they pass on my system (and I've run them > since applying too), so that there is really likely to be some kind of > difference between machines.
Right, Travis seems happy too so most likely it's something to do with my setup. I'm open to ideas about what might cause this. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
