Short story: I have been able to reproduce it in 0.7.2 but I was never 100% clear what caused it in 0.7.0 and it hasn't had enough priority to surface to the top of my queue. If and when you do update to 0.7.2 (btw, 0.7.3 will be out Soon), could you please check to see if this is still a problem?
Thanks! - Rob . On Fri, Jun 24, 2011 at 12:17 AM, Victor Torres <vit...@poli.ufrj.br> wrote: > Hello Rob, > > Thanks for the fast reply.. > > I'm running 0.7.0. > > I was writing some code for the 0.7.2, but only have 0.7.0 currenty running. > > I'm unable to test 0.7.2 for the next few days so was wondering if it > was fixed in 0.7.2. > > > Victor T. > > On 24 June 2011 03:32, Rob Sherwood <rob.sherw...@stanford.edu> wrote: >> HI Victor, >> >> My guess is this is a bug ( see : >> https://openflow.stanford.edu/bugs/browse/FLOWVISOR-32) >> >> I'm trying to figure out what causes this and if it's still an issue >> with current code: what version are you running? >> >> Thanks, >> >> - Rob >> . >> >> >> >> On Thu, Jun 23, 2011 at 11:03 PM, Victor T. <vit...@poli.ufrj.br> wrote: >>> Hello, >>> >>> I was testing some of the FlowVisor's functions and wondered about the >>> response of getSliceStats: >>> >>> Why does it return multiple lines referring to the same switch? I mean, the >>> lines do (apparently) contain different data, but yet are a lot of lines. >>> >>> Does anyone know why there are so many lines? >>> >>> >>> Thanks in advance, >>> >>> Peace! >>> Victor T. >>> _______________________________________________ >>> openflow-discuss mailing list >>> openflow-discuss@lists.stanford.edu >>> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss >>> >> > _______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
