Re: [OPW PATCH V4] tools: xl: refactor code to parse network device options

[Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>]

On Fri, Oct 24, 2014 at 11:58:28AM +0300, Alexandra Sandulescu wrote:
> Hello,
> 
> I have tested stuff by hand (I took the code and created some structures -
> a bit of workaround let's say). Should I test it with OSSTest too?

No need to run the OSSTest, that was more for my own curiosity.

> What I understood from Wei is that he tested my patch. Maybe I got it wrong.
> 
> Thank you all,
> Alex
> 
> On Fri, Oct 24, 2014 at 11:01 AM, Ian Campbell <Ian.Campbell@citrix.com>
> wrote:
> 
> > On Thu, 2014-10-23 at 19:08 -0400, Konrad Rzeszutek Wilk wrote:
> > > > He said the code *path*, not the code, IOW I would read that as "would
> > > > be tested", NOT "has been tested".
> > > >
> > >
> > > Aye. In which case let's wait for Alexandra's response to the testing
> > > that Wei asked for.
> >
> > Alexandra replied to me (privately) a couple of days ago confirming that
> > she has tested both code paths.
> >
> > > On a related note - one can setup OSSTest on ones own network, fairly
> > easy right?
> >
> > Right in "standalone mode". It's far easier than it once was and we've
> > been squashing speedbumps as new people try it.
> >
> > You do need some infrastructure such as PXE and dhcp and at least two
> > machines (controller + test host). I think it would be overkill for a
> > change of this magnitude (if that's what you were driving at).
> >
> > I think
> >
> > http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;h=9a85549cb600fa5be91bcbae6605f78616db63da;hb=2aa4fe7a4b138e5e88387af66f4fe14039a1f7ea
> > is the best starting point for osstest, including standalone mode operation.
> >
> > Ian.
> >
> >