[openstack-dev] [neutron][gate] please stop approving patches until netaddr issue is solved
Paul Michali
pc at michali.net
Mon Aug 31 15:46:56 UTC 2015
For all VPN commits that I had previously gave a +2, I added a WIP (not
ready for review).
Regards,
On Mon, Aug 31, 2015 at 11:34 AM Kevin Benton <blak111 at gmail.com> wrote:
> Thanks for the clarification. I had thought that, after a short period of
> time, changes would always have to go back through the check tests before
> hitting the gate.
>
> On Mon, Aug 31, 2015 at 8:27 AM, Clark Boylan <cboylan at sapwetik.org>
> wrote:
>
>> If the check tests ran prior to the netaddr release and got a +1 any
>> approvals will put them straight into the gate. They will only go
>> through check first (and fail there) if they do not already have a +1
>> from Jenkins.
>>
>> When they fail in the gate they reset all the changes behind them. When
>> you have several changes that will fail like this you end up reseting
>> over and over until the queue processes each one at the head of the
>> queue, removes them, and leaves a -2 vote for the failed gate run.
>>
>> On Mon, Aug 31, 2015, at 08:20 AM, Kevin Benton wrote:
>> > Why would they reset the gate? Shouldn't they just fail the check test?
>> >
>> > On Mon, Aug 31, 2015 at 6:18 AM, Ihar Hrachyshka <ihrachys at redhat.com>
>> > wrote:
>> >
>> > > Hi all,
>> > >
>> > > I see neutron folks pushing more neutron patches into the gate. They
>> are
>> > > all doomed to fail until [1] is resolved. So please stop approving
>> patches,
>> > > we only make harm by resetting the gate, with no chance to pass it.
>> > >
>> > > PS: it is the same for all neutron stadium projects, so *aas and
>> > > python-networking-* folks, please also avoid +W until the situation is
>> > > cleared.
>> > >
>> > > [1]: https://bugs.launchpad.net/neutron/+bug/1490380
>> > >
>> > > Ihar
>> > >
>> __________________________________________________________________________
>> > > OpenStack Development Mailing List (not for usage questions)
>> > > Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> > >
>> >
>> >
>> >
>> > --
>> > Kevin Benton
>> >
>> __________________________________________________________________________
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe:
>> > OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
> --
> Kevin Benton
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150831/d3af7928/attachment.html>
More information about the OpenStack-dev
mailing list