this should already be solved by moving find bugs code to check-patch.sh

This shouldn't happen anymore on master since the code was moved to check-patch.

We are waiting for dev to backport for 4.1 so you won't see this issue there as well.

cc

Look after patch set 4 at Mar 1 11:58 AM

How do you know that findBugs job should've being running? There is no
evidence for starting that on patchset 4 in the comments.
There are comments for the 2 other jobs that mention their number out of 3,
but there is nothing telling a thing about the 3rd job.

On Tue, Mar 7, 2017 at 8:00 PM, Yevgeny Zaspitsky (oVirt JIRA) <

The comment in gerrit includes only 2 jobs and both are successful.
Here is the copy of the comment by Jenkins CI:

Patch Set 4: Continuous-Integration-1

Build Failed

http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/19428/
: SUCCESS

http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc25-x86_64/3480/
: SUCCESS

On Tue, Mar 7, 2017 at 1:03 PM, Gil Shinar (oVirt JIRA) <

At that time three jobs has been executed. Two check patches and one find bugs. We do not have history of the find bugs job but you can see that only these two check patches has returned success status.
Do you happen to know what were the results of this find bug job?

at 01/03 13:14

On Tue, Mar 7, 2017 at 9:41 AM, Gil Shinar (oVirt JIRA) <