Re: [openstack-dev] [python-*client] py33 jobs seem to be failing

2014-12-19 Thread Amit Gandhi
Is there an ETA for this fix? Thanks Amit. On Dec 17, 2014, at 3:38 PM, Jeremy Stanley fu...@yuggoth.org wrote: On 2014-12-17 11:09:59 -0500 (-0500), Steve Martinelli wrote: [...] The stack trace leads me to believe that docutils or sphinx is the culprit, but neither has released a new

Re: [openstack-dev] [python-*client] py33 jobs seem to be failing

2014-12-19 Thread Davanum Srinivas
Amit, from chatter on infra irc,. should be almost done if not already done. if you see any jobs fail recheck, you may want to hop onto irc. thanks, dims On Fri, Dec 19, 2014 at 11:19 AM, Amit Gandhi amit.gan...@rackspace.com wrote: Is there an ETA for this fix? Thanks Amit. On Dec 17,

Re: [openstack-dev] [python-*client] py33 jobs seem to be failing

2014-12-19 Thread Steve Martinelli
...@rackspace.com wrote on 12/19/2014 11:19:46 AM: From: Amit Gandhi amit.gan...@rackspace.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: 12/19/2014 11:28 AM Subject: Re: [openstack-dev] [python-*client] py33 jobs seem

Re: [openstack-dev] [python-*client] py33 jobs seem to be failing

2014-12-19 Thread Jeremy Stanley
On 2014-12-19 11:32:02 -0500 (-0500), Steve Martinelli wrote: Seems like https://review.openstack.org/#/c/142561/ fixed the issue. As there haven't been any hits in logstash in roughly 24hrs, and we're getting clean builds in python-keystoneclient and openstackclient. [...] Apparently there

[openstack-dev] [python-*client] py33 jobs seem to be failing

2014-12-17 Thread Steve Martinelli
Wondering if anyone can shed some light on this, it seems like a few of the clients have been unable to build py33 environments lately:

Re: [openstack-dev] [python-*client] py33 jobs seem to be failing

2014-12-17 Thread Jeremy Stanley
On 2014-12-17 11:09:59 -0500 (-0500), Steve Martinelli wrote: [...] The stack trace leads me to believe that docutils or sphinx is the culprit, but neither has released a new version in the time the bug has been around, so I'm not sure what the root cause of the problem is. It's an unforeseen