Open Stack

On Wed, Feb 1, 2017 at 7:42 AM, Armando M. <armamig at gmail.com> wrote:
>
>
> On 1 February 2017 at 07:29, Ihar Hrachyshka <ihrachys at redhat.com> wrote:
>>
>> Hi all,
>>
>> lately I see the requirements bot proposing new rebases for its
>> patches (and bumping existing patch sets from the gate queue) every
>> second hour, at least for Neutron [1], which makes it impossible to
>> land the patches, and which only makes gate pre-release situation
>> worse. On top of that, the proposed rebases don't really add anything
>> material to the sync patch, no new version changes and such.
>>
>> I think we had some guards against such behavior before, so I wonder
>> if they were broken or removed lately? Any plans to fix that?
>>
>> It would be nice to be able to land the update before RC1 is cut off,
>> but at this point, it does not seem realistic.
>>
>> [1] https://review.openstack.org/#/c/423645/
>>
>
> Let's stop merging until the bot proposal change lands. That ought to stop
> the spurious rebase!
>
> Hard times require hard measures!!

That's assuming it's triggered by neutron merges. It may as well be
requirements merges that trigger rebases. Something that I believe
requirements team will help us to understand.

Ihar