[openstack-dev] [all] fix latency on requirements breakage

Tom Fifield tom at openstack.org
Tue Nov 18 13:53:01 UTC 2014

On 18/11/14 18:51, Thierry Carrez wrote:
> Christopher Yeoh wrote:
>> On Tue, Nov 18, 2014 at 9:32 AM, Sean Dague <sean at dague.net
>> <mailto:sean at dague.net>> wrote:
>>     waiting extra long for valid test results. People don't realize their
>>     code can't pass and just keep pushing patches up consuming resources
>>     which means that parts of the project that could pass tests, is backed
>>     up behind 100% guarunteed failing parts. All in all, not a great system.
>> Maybe a MOTD at the top of http://review.openstack.org could help here?
>> Have a button
>> that the QA/infra people can hit when everything is broken that puts up
>> a message
>> there asking people to stop rechecking/submitting patches.
> We can already ask statusbot
> (http://ci.openstack.org/irc.html#statusbot) to show up messages on
> status.openstack.org and log them to
> https://wiki.openstack.org/wiki/Infrastructure_Status
> It's just not used as much as it used to for CI breakage those days.

I have to say, extending statusbot to do MOTD on
http://review.openstack.org sounds like a great idea to me. It also
sounds like one of those changes to gerrit that might actually be in the
'achievable' bucket :D



More information about the OpenStack-dev mailing list