[openstack-dev] [all][infra] NOT_REGISTERED to be or not to be

Lenny Verkhovsky lennyb at mellanox.com
Mon Aug 1 15:53:12 UTC 2016


Currently in some cases[1] CI sets a comment on the patch set as NOT_REGISTERED.

Those comments are very hard to monitor for CI operators and have noisy value for the developers.

Maybe a better solution is not commenting in such cases at all as discussed in [2].

If a developer is missing some important CI comments, it can rechecked later or sent an email to CI owner.

[1] No valid slaves
       Not all jobs are registered due to zuul restart for instance

[2] http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2016-08-01.log.html

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160801/08355792/attachment.html>

More information about the OpenStack-dev mailing list