[openstack-dev] [all] Moving coverage jobs to check queue

Jeremy Stanley fungi at yuggoth.org
Tue Feb 14 15:38:31 UTC 2017

On 2017-02-14 11:50:46 +1100 (+1100), Ian Wienand wrote:
> Some projects run in both check and post which seems unnecessary.

The argument in favor of doing both is that one helps you get a
rough idea of the coverage increase/decrease a proposed change may
bring, while the other allows you to accurately track coverage
trending over time for a given branch. Also if the check pipeline
job for it is voting, it helps you avoid merging a change that might
break coverage checking (note this is separate from how some
projects also modify it to fail on any coverage decrease, which is a
bit more problematic since there can be valid reasons to decrease
coverage on occasion).

> The coverage job results in post are quite hard to find. You need to
> firstly know the job even runs, then find the correct commit sha
> (which is probably the merge commit, not the one in gerrit) and then
> know how to manually navigate the logs.openstack.org file-hierarchy.
> It's probably no surprise that according to apache logs, nobody has
> accessed a post coverage-job output at all within about the last
> month. Also, as per the prior email, if the job is actually failing
> you get no notification at all.

Tracking coverage jobs in the health dashboard may alleviate that
(and could even bring trending graphs depending on how it's
implemented). It would, however, require someone to write the
necessary glue.
Jeremy Stanley

More information about the OpenStack-dev mailing list