[openstack-dev] [oslo]: some functional tests for the olso.messaging API

Doug Hellmann doug.hellmann at dreamhost.com
Mon Mar 31 15:41:07 UTC 2014

On Mon, Mar 31, 2014 at 11:36 AM, Gordon Sim <gsim at redhat.com> wrote:

> On 03/31/2014 04:11 PM, Doug Hellmann wrote:
>> On Mon, Mar 31, 2014 at 8:54 AM, Gordon Sim <gsim at redhat.com
>> <mailto:gsim at redhat.com>> wrote:
>>     Another slight annoyance from the testing pov is that the API
>>     provides no way of determining when a server is 'ready' i.e. when
>>     its subscriptions are in place. I had to work around this for qpid
>>     and rabbit with a short sleep, which is always a bit nasty.
>> Are you saying that creating the subscription doesn't block until it is
>> ready?
> With the blocking executor, if I call start() on the server returned by
> get_rpc_server(), then the start call blocks (until it detects stop has
> been called). It does look like this is just an issue for that executor
> though, since the eventlet executor will return after the listen has been
> issued.

That's how I would expect them to work. Is the eventlet executor not
"ready" then?


> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140331/79576693/attachment.html>

More information about the OpenStack-dev mailing list