On Wed, Nov 28, 2018 at 10:32 PM Dafna Ron <dron@redhat.com> 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?