see inline comment On Mon, Jul 18, 2016 at 2:09 PM, Andreas Jaeger <a...@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.
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
