Open Stack

see inline comment

On Mon, Jul 18, 2016 at 2:09 PM, Andreas Jaeger <aj at suse.com> wrote:

> While looking at coverage jobs to enable them to allow use of
> constraints in post jobs (something which has just been introduced and
> needs some more testing before we take on the other jobs), I noticed
> that we have quite a few coverage
> jobs that are failing.
>
> In general, I think coverage jobs should be run as check job so
> that you know how the coverage changes. Running them only in the post
> job means that in practice nobody sees the output of the job.
>

Yes please! I never understood why they were run as post jobs. In keystone
we've had it running as a check/gate job for a while without hiccups.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160718/4ba3fc7c/attachment.html>