----- Original Message -----
From: "David Caro" <dcaro@redhat.com> To: "Francesco Romani" <fromani@redhat.com> Cc: "infra" <infra@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 :\ Thanks, -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani