[ovs-dev] [RFC] ovsdb: implement read-only remote connection type

Lance Richardson lrichard at redhat.com
Thu Oct 13 21:28:04 UTC 2016


> From: "Ben Pfaff" <blp at ovn.org>
> To: "Lance Richardson" <lrichard at redhat.com>
> Cc: dev at openvswitch.org, jpetit at ovn.org
> Sent: Thursday, October 13, 2016 5:08:42 PM
> Subject: Re: [ovs-dev] [RFC] ovsdb: implement read-only remote connection type
> 
> On Thu, Oct 13, 2016 at 03:08:46PM -0400, Lance Richardson wrote:
> >  Doing 'make check TESTSUITEFLAGS="1876-1881"' executes these test
> >  cases:
> >     1876: ovsdb-server/read-only ptcp connection          ok
> >     1877: ovsdb-server/read-only punix connection         ok
> >     1878: ovsdb-server/read-only pssl connection          ok
> >     1879: ovsdb-server/read-only tcp connection           ok
> >     1880: ovsdb-server/read-only unix connection          ok
> >     1881: ovsdb-server/read-only ssl connection           ok
> > 
> >  But doing 'make check TESTSUITEFLAGS="-k read-only"' only executes
> >  these:
> >     1876: ovsdb-server/read-only ptcp connection          ok
> >     1877: ovsdb-server/read-only punix connection         ok
> >     1879: ovsdb-server/read-only tcp connection           ok
> >     1880: ovsdb-server/read-only unix connection          ok
> > 
> >  Shouldn't they all match the "read-only" keyword??
> 
> Autotest is really dumb when it comes to defining a "word".  It thinks
> that "ovsdb-server/read-only" is a single word.
> 
> (Some of them did match because you included AT_KEYWORDS([read-only]) in
> them.)
> 

I thought I had checked that, but you're absolutely correct. It's not
just autotest that's challenged, apparently.

Thanks,

   Lance



More information about the dev mailing list