Hi all,
I've been working on a patch to ensure that all tempest tests are able to
handle rate limiting errors with automatic retries [0].
API tests already implement retries, however scenario tests don't, the main
reason being that scenario tests rely on the official python bindings, most
of
Frittoli,
I don't think that this is a good idea. Because the main role of tempest is
to ensure that cloud works. So if it doesn't work we should change
something in deployment configuration or code to fix it. Not just hide with
monkey patches in tempest.
Probably you should try to implement
questions)
Subject: Re: [openstack-dev] [qa][python-bindings] Reries on HTTP error in
python bindings
On Wed, Jan 15, 2014 at 5:28 AM, Frittoli, Andrea (Cloud Services)
fritt...@hp.com wrote:
Hi all,
I've been working on a patch to ensure that all tempest tests are able to
handle rate