On Wed, Nov 28, 2018 at 10:32 PM Dafna Ron <[email protected]> wrote: > 1. it did not break ost. one failed CQ run on for one project does not > mean that ost is broken :) >
Ok, broke the change queue :-) > 2. the build was reported as failed even though there was no actual > failure as CQ did not even start to run. if you look at the error, you can > see that CQ actually exited because the package was failed to be build. so > no package -> no CQ run. > > *18:25:48* vdsm_standard-on-merge (33) failed building > > The vdsm build is failing with this error; > > *20:04:31* [build-artifacts.fc28.s390x] *** WARNING: mangling shebang in > /usr/libexec/vdsm/hooks/before_nic_hotplug/50_macspoof from #!/usr/bin/python > to #!/usr/bin/python2. This will become an ERROR, fix it manually!*20:04:31* > [build-artifacts.fc28.s390x] *** WARNING: mangling shebang in > /usr/libexec/vdsm/hooks/before_device_create/50_macspoof from > #!/usr/bin/python to #!/usr/bin/python2. This will become an ERROR, fix it > manually!*20:04:32* [build-artifacts.fc28.s390x] *** WARNING: mangling > shebang in /usr/libexec/vdsm/hooks/before_vm_start/50_fileinject from > #!/usr/bin/python to #!/usr/bin/python2. This will become an ERROR, fix it > manually! > > This looks like a warning not an error. Maybe the stdci change added fedora 28 build on s390x, that was not enabled before the patch? Can we test this using manual build-artifacts job? Or maybe we need to add build-artifacts job to check-patch, to make sure that every patch can be built on all platforms? > > On Wed, Nov 28, 2018 at 7:52 PM Nir Soffer <[email protected]> wrote: > >> On Wed, Nov 28, 2018 at 9:14 PM oVirt Jenkins <[email protected]> wrote: >> >>> Change 95559,13 (vdsm) is probably the reason behind recent system test >>> failures in the "ovirt-master" change queue and needs to be fixed. >>> >>> This change had been removed from the testing queue. Artifacts build >>> from this >>> change will not be released until it is fixed. >>> >>> For further details about the change see: >>> https://gerrit.ovirt.org/#/c/95559/13 >> >> >> This change added stdci v2. How can it break OST? >> >> Nir >> _______________________________________________ >> Infra mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/[email protected]/message/OBJ3SGQBYT2GVCJWAYQNFMK745YSDXPD/ >> >
_______________________________________________ Infra mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/ZWEFQ7IW25VSOUEF4GTJDOF6MNELV75G/
