[openstack-dev] [neutron] [driverlog] Tail-f CI and it's lack of running and it's DriverLog status

Kyle Mestery mestery at noironetworks.com
Tue Jun 10 15:27:52 UTC 2014


On Tue, Jun 10, 2014 at 10:15 AM, Ilya Shakhat <ishakhat at mirantis.com> wrote:
> Hi!
>
> Tail-f driver seems to be configured correctly. DriverLog will poll Gerrit
> in the next 4 hours and update driver details screen.
>
> Regarding green mark on summary screen - it is shown for those drivers that
> have configured CI and CI ran at least once. But it doesn't take into
> account when the last successful run was. I suppose this mark may be changed
> to something like "CI health" and be green only if tests passed on master
> and were run during the last month.
>
It would be great if this could be in the last few days. Third party
CI systems should be testing enough upstream commits so they should
run at least every few days.

> Thanks,
> Ilya
>
>
> 2014-06-10 18:33 GMT+04:00 Luke Gorrie <luke at tail-f.com>:
>>
>> Howdy!
>>
>> Here is a successful Sandbox test from right now:
>> https://review.openstack.org/#/c/99061/. I don't immediately see how to list
>> all historical sandbox tests. (The previous ones are from before the Summit
>> anyway.)
>>
>> I enabled the CI for the openstack/neutron Gerrit feed now. Here is a
>> change that it tested right now: https://review.openstack.org/#/c/95526/.
>> (Voting is disabled on the account and the config conservatively is set to
>> vote 0 on failure.)
>>
>>> Yes, I believe you can just submit a patch to DriverLog to reflect the
>>> current status.
>>
>>
>> DriverLog is sourced from default_data.json
>> (https://github.com/stackforge/driverlog/blob/master/etc/default_data.json#L1007)?
>> If so then it does reflect the current status:
>>
>>             "ci": {
>>                 "id": "tailfncs",
>>                 "success_pattern": "Successful",
>>                 "failure_pattern": "Failed"
>>             }
>>
>> i.e. it specifies which CI account is associated with this driver, and
>> that corresponds to a CI that is now up and running.
>>
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>



More information about the OpenStack-dev mailing list