Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

https://gerrit.ovirt.org/#/c/73161 marked with CI-1

Description

Jenkins CI marked the ${subject} patch with CI-1, despite of 2 successful
CI runs it had.

Activity

Show:

Eyal Edri June 27, 2017 at 2:47 PM

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

Eyal Edri May 25, 2017 at 12:07 PM

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

Former user March 8, 2017 at 7:53 AM

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

Former user March 7, 2017 at 6:06 PM

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) <

Former user March 7, 2017 at 6:00 PM

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) <

Fixed

Details

Assignee

Reporter

Blocked By

Priority

Created March 6, 2017 at 1:21 PM
Updated July 2, 2017 at 2:08 PM
Resolved June 27, 2017 at 2:47 PM