[ovirt-devel] ovirt-provider-ovn_master_build-artifacts-el7-x86_64 Failing Due to Spec Problem
Dan Kenigsberg
danken at redhat.com
Sun Aug 27 14:55:43 UTC 2017
On Sun, Aug 27, 2017 at 12:24 PM, Eyal Edri <eedri at redhat.com> wrote:
> Adding patch author and maintainers.
>
> On Fri, Aug 25, 2017 at 11:40 AM, Anton Marchukov <amarchuk at redhat.com>
> wrote:
>>
>> Hello All.
>>
>> Just noted that change queue job [1] for ovirt-provider-ovn started to
>> fail consistently while the actual reason for that seems to be RPM build
>> failure at [2]:
>>
>> 14:47:42 Checking for unpackaged file(s): /usr/lib/rpm/check-files
>> /home/jenkins/workspace/ovirt-provider-ovn_master_build-artifacts-el7-x86_64/ovirt-provider-ovn/rpmbuild/BUILDROOT/ovirt-provider-ovn-1.1-2.20170824144740.gitcf66669.el7.centos.x86_64
>> 14:47:42 error: Installed (but unpackaged) file(s) found:
>> 14:47:42 /usr/share/doc/ovirt-provider-ovn/README.adoc
>> 14:47:42
>> 14:47:42
>> 14:47:42 RPM build errors:
>> 14:47:42 Installed (but unpackaged) file(s) found:
>> 14:47:42 /usr/share/doc/ovirt-provider-ovn/README.adoc
>> 14:47:42 make: *** [rpm] Error 1
>> 14:47:42 Took 2 seconds
>>
>>
>> Possible root cause for that is [3] (Install README). However, I see CI
>> passed there within the change at least before the rebase.
>>
>>
>> [1]
>> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1996/console
>> [2]
>> http://jenkins.ovirt.org/job/ovirt-provider-ovn_master_build-artifacts-el7-x86_64/142/console
>> [3] https://gerrit.ovirt.org/#/c/80801/
>>
>> --
>> Anton Marchukov
>> Team Lead - Release Management - RHV DevOps - Red Hat
Thanks for your report, Anton. I'm sure that Marcin would fix this by tomorrow.
However, we see here another case where a patch
https://gerrit.ovirt.org/#/c/80801/ triggers a job
http://jenkins.ovirt.org/job/ovirt-provider-ovn_master_build-artifacts-el7-x86_64/134/
the job fails, but the patch is not marked with -1, and the patch
author does not get an email.
I know that the CI team is paying attention to this glitch, but please
note that it's here, too.
Marcin, in vdsm's automation/check-patch we trigger built-artifacts in
case a Makefile or a spec has changed. How about doing the same in
ovirt-provifder-ovn?
Regards,
Dan.
More information about the Devel
mailing list