How to remove bad Jenkins CI score

[David Caro]

On 09/17, Francesco Romani wrote:
> ----- Original Message -----
> > From: "David Caro" <dcaro at redhat.com>
> > To: "Francesco Romani" <fromani at redhat.com>
> > Cc: "infra" <infra at ovirt.org>
> > Sent: Thursday, September 17, 2015 3:47:44 PM
> > Subject: Re: How to remove bad Jenkins CI score
> > 
> > On 09/17, Francesco Romani wrote:
> > > ----- Original Message -----
> > > > From: "David Caro" <dcaro at redhat.com>
> > > > To: "Francesco Romani" <fromani at redhat.com>
> > > > Cc: "infra" <infra at ovirt.org>
> > > > Sent: Thursday, September 17, 2015 3:38:24 PM
> > > > Subject: Re: How to remove bad Jenkins CI score
> > > > 
> > > 
> > > > > > You can see the full test output here:
> > > > > > http://jenkins.ovirt.org/job/vdsm_3.6_check-patch-fc22-x86_64/37/console
> > > > > > The new invocation is still running ATM here:
> > > > > > http://jenkins.ovirt.org/job/vdsm_3.6_check-patch-fc22-x86_64/74/console
> > > > > 
> > > > > Thanks! But the old score is still here, despite
> > > > 
> > > > 
> > > > That's because the +1 is for the patchset 1, and the -1 is on patchset 3
> > > > (it
> > > > was carried over from patchset 1 because the 2 and 3 did no code changes)
> > > > 
> > > > The jobs don't trigger for patches that don't change any code, and as
> > > > such,
> > > > it
> > > > does not update the value for patch 3.
> > > > The only way to allow that would be to trigger on any patch, but that
> > > > would
> > > > overload jenkins.
> > > 
> > > Yes, that makes sense.
> > > 
> > > > In any case, it should not be blocking anything.
> > > 
> > > Well, in this unfortunate case of one bogus/temporary initial failure yes,
> > > because
> > > I don't have the "submit" button on my screen :\
> > 
> > You are not part of the maintainers for that branch (same as master)
> > 
> > https://gerrit.ovirt.org/#/admin/groups/31,members
> 
> Sorry, I don't follow.
> I already merged patches[0] in vdsm ovirt-3.6, and I have the submit button[1]
> in the screen of the following patch of the same branch[2].


My bad, you are as you should, it turns out that the flag is wrongly configured
specifycally on vdsm (as we did not roll out the whole flags initiative, it got
'half deployed').

I've just changed it, hit f5


> 
> Please check the attached screenshot
> 
> +++
> 
> [0] last example: https://gerrit.ovirt.org/#/c/46102/
> [1] Unless it is a trap :)
> [2] but I don't want to merge them out of order
> 
> -- 
> Francesco Romani
> RedHat Engineering Virtualization R & D
> Phone: 8261328
> IRC: fromani


> _______________________________________________
> Infra mailing list
> Infra at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra


-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D

Tel.: +420 532 294 605
Email: dcaro at redhat.com
Web: www.redhat.com
RHT Global #: 82-62605
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20150917/83a1f14f/attachment.sig>