Re: [openstack-dev] [all] Reviewing coverage jobs set up

On 2016-08-04 09:36:18 -0400 (-0400), Jim Rollenhagen wrote: [...] > Nice! FWIW, it's also documented here: > http://docs.openstack.org/infra/manual/developers.html#automated-testing I just proposed a note clarifying the situation with URLs for merge commits too, since that seems to have been

Re: [openstack-dev] [all] Reviewing coverage jobs set up

On Thu, Aug 04, 2016 at 09:24:15AM -0400, Doug Hellmann wrote: > Excerpts from Kiall Mac Innes's message of 2016-08-04 01:27:23 +0100: > > On 18/07/16 20:14, Jeremy Stanley wrote: > > > Note that this will only be true if the change's parent commit in > > > Gerrit was the branch tip at the time it

Re: [openstack-dev] [all] Reviewing coverage jobs set up

Excerpts from Kiall Mac Innes's message of 2016-08-04 01:27:23 +0100: > On 18/07/16 20:14, Jeremy Stanley wrote: > > Note that this will only be true if the change's parent commit in > > Gerrit was the branch tip at the time it landed. Otherwise (and > > quite frequently in fact) you will need to

Re: [openstack-dev] [all] Reviewing coverage jobs set up

On 18/07/16 20:14, Jeremy Stanley wrote: Note that this will only be true if the change's parent commit in Gerrit was the branch tip at the time it landed. Otherwise (and quite frequently in fact) you will need to identify the SHA of the merge commit which was created at the time it merged and

Re: [openstack-dev] [all] Reviewing coverage jobs set up

The following coverage jobs are still wrongly setup, I've proposed a change now to remove them from our infra setup [1]: * cloudkitty-dashboard * murano-agent * nova-docker * os-net-config * poppy * sahara-dashboard * solum-dashboard * trove-dashboard * turbo-hipster

Re: [openstack-dev] [all] Reviewing coverage jobs set up

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

Re: [openstack-dev] [all] Reviewing coverage jobs set up

On Mon, Jul 18, 2016 at 4:11 PM, Andreas Jaeger wrote: > You're welcome to send a patch for openstack-infra/project-config repo > and update zuul/layout.yaml to add the job to the check queue of nova. Done, thanks for pointing me in the right direction!

Re: [openstack-dev] [all] Reviewing coverage jobs set up

On 07/18/2016 10:03 PM, Diana Clarke wrote: > On Mon, Jul 18, 2016 at 2:09 PM, Andreas Jaeger wrote: >> 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

Re: [openstack-dev] [all] Reviewing coverage jobs set up

On Mon, Jul 18, 2016 at 2:09 PM, Andreas Jaeger wrote: > 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. I look at the post queue

Re: [openstack-dev] [all] Reviewing coverage jobs set up

see inline comment On Mon, Jul 18, 2016 at 2:09 PM, 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

Re: [openstack-dev] [all] Reviewing coverage jobs set up

On 2016-07-18 20:09:54 +0200 (+0200), Andreas Jaeger wrote: [...] > Btw. if you want to get the output of the post job, check the git SHA. > logs are found at ``http://logs.openstack.org/ commit SHA>/``. For example, if a change is committed with > the sha 'deadbeef123456', the logs will be found

[openstack-dev] [all] Reviewing coverage jobs set up

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