The commit that introduced flow_wc_map is dated 18/Oct/2014. I notice that flow.c does not have any commits after Jun/2014 in the 2.3 branch, so that explains why Joe hasn't seen the issue in that branch.
I'll take Joe's advice and try to clean up the test and submit it to the delivery mailing list. The packet is just one from the neighbor discovery test with type and code changed. I'll try to make it more well-formed. Your comment about closing quote probably explains Ben's original comment, I'll play around with that tonight. Tony On Thu, Jun 11, 2015 at 2:16 PM, Ben Pfaff <[email protected]> wrote: > On Wed, Jun 10, 2015 at 06:54:55PM -0700, Joe Stringer wrote: > > I suspect if we'd thought of particular additional cases, we would > > have added them. If there are more problems that oftest is showing up, > > fixing those bugs and adding tests to show that the fix works would be > > appropriate. Generally the CI we use (eg travis) doesn't run the > > oftest framework, so this would be a way to ensure that there aren't > > regressions in areas like this. > > I have a pile of patches that fix a lot of bugs found by oftest (and > another pile that fixes bugs in oftest), which I have not yet posted, > but I don't remember anything like this showing up. >
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
