On Mon, Jul 18 2016, Andreas Jaeger 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.
I had no idea these jobs existed and we never used them. So I think it's safe to disable them for telemetry projects and save some CPU time from the gate for other things. (Not saying the info is useless, but as far as we're concern, running it From time to time locally and trying to check what might not be covered is largely good enough.) -- Julien Danjou /* Free Software hacker https://julien.danjou.info */
signature.asc
Description: PGP signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
