fe3f04d9d78e4fec13bcc3693c2b134aa65ef9ca

Project: openstack-infra/storyboard ca537c255a096a1ebd385dabaf27d54f6369ce99 Better handle pika connection errors It seems like pika may raise AttributeError when the connection is closed, as describe here: https://github.com/pika/pika/issues/638, resulting in this error displayed on the webclient: 500: POST /storyboard_api/tasks: 'NoneType' object has no attribute 'send' This change adds AttributeError to the ConnectionClosed except. Change-Id: Iffa1ef1998379097b32d699a360b5de9277c01ed
…
…
…
…
…
…
…
…
…
…
…
…
…
…
OpenStack Tracking Repo
zuul gates all of the contained projects in an effective single timeline. This means that OpenStack, across all of the projects, does already have a sequence of combinations that have been explicitly tested, but it's non-trivial to go from a single commit of a particular project to the commits that were tested with it.
Gerrit's submodule tracking feature will update a super project every time a subproject is updated, so the specific sequence created by zuul will be captured by the super project commits.
This repo is intended to be used in a read-only manner. Any commit in this repo will get a collection of commits in the other repos that have explicitly been tested with each other, if that sort of thing is important to you.
Description
Languages
Python
100%