On 06/23/2015 08:13 AM, John Garbutt wrote: >>>>> The question for the nova team is, shall we make the tempest-dsvm-cells >>>>> job voting on nova changes knowing that the gate can be broken with a >>>>> change to tempest that isn't caught in the regex? In my opinion I think >>>>> we should make it voting so we don't regress cells with changes to nova >>>>> that go unnoticed with the non-voting job today. Cells v2 is a nova >>>>> priority for Liberty so we don't want setbacks now that it's stable. > > I would be tempted to risk it, given the large gain, but I am a little > biased too. > > But with us controlling the regex, that seems a much easier call to say yes.
Right, with the REGEX back in control of the Nova team, we can just temporarily drop any failing tests from Tempest changes until fixes or reverts happen. I honestly think this kind of asymetric decoupling is a thing we're going to need to get good at, because everything can't cross gate with everything else. Otherwise we'll go back to 100 hr gate queues and bugs that take a week to resolve in the intertwining. -Sean -- Sean Dague http://dague.net __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev