Please note: ovirt-hosted-engine-ha builds are failing
Hi, Builds of ovirt-hosted-engine-ha had been failing for the last 3 merged patches. This is currently not being reported on gerrit because of a known issue we are working to fix [1]. The 1st patch where builds started failing is: https://gerrit.ovirt.org/#/c/81224/ Failing build jobs for this patch are the following: - http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_build-artifacts-e... - http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_build-artifacts-f... Build logs for failing jobs are respectively at these locations: - http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_build-artifacts-e... - http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_build-artifacts-f... [1]: https://ovirt-jira.atlassian.net/browse/OVIRT-1502 -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
Hi Barak, maybe you should stop setting CI+1 before that is fixed? Martin On Thu, Aug 31, 2017 at 8:36 AM, Barak Korren <bkorren@redhat.com> wrote:
Hi,
Builds of ovirt-hosted-engine-ha had been failing for the last 3 merged patches.
This is currently not being reported on gerrit because of a known issue we are working to fix [1].
The 1st patch where builds started failing is: https://gerrit.ovirt.org/#/c/81224/
Failing build jobs for this patch are the following: - http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_build-artifacts-e... - http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_build-artifacts-f...
Build logs for failing jobs are respectively at these locations: - http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_build-artifacts-e... - http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_build-artifacts-f...
[1]: https://ovirt-jira.atlassian.net/browse/OVIRT-1502
-- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
On 31 August 2017 at 11:07, Martin Sivak <msivak@redhat.com> wrote:
Hi Barak,
maybe you should stop setting CI+1 before that is fixed?
The CI flag is set before the patch is merged, and this reports fine to gerrit. I'm talking here about stuff that happens after you merge, when the flag is no longer relevant. As a side note, the actual reason for failing to report is because our post-merge code is trying to set the flag, and it seems that at some point Gerrit stopped allowing this to happen. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
participants (2)
-
Barak Korren -
Martin Sivak