All: There are at least a couple of issues that are currently impacting the trove gate and I'm getting to the bottom of it. The currently known problems are being handled in a single commit[1].
This currently emcompasses the issues identified in three independent commits, none of which will be able to merge by themselves [2], [3], and [4]. There is at least one more issue that I have to wrestle to the ground and it appears to be some change to the structure of oslo_context that isn't immediately apparent (at least that's the current hunch). In the meanwhile, rechecks and changes to trove, and python-troveclient will merely fail after taking up some useless time in the gate. I'll try and get this resolved soon, sorry for the delay. -amrith [1] https://review.openstack.org/#/c/426535/ [2] https://review.openstack.org/#/c/425857/ [3] https://review.openstack.org/#/c/423086/ [4] https://review.openstack.org/#/c/412497/ -- Amrith Kumar GPG: 0x5e48849a9d21a29b
smime.p7s
Description: S/MIME cryptographic signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
