Hi All, 'check-patch' pipeline for OST has currently a huge queue of jobs to be executed, some stuck since 14 hrs [1]. When testing patches for OST please consider trimming down the triggered pipelines like this [2], and marking the patch with "WIP" until it's ready. Also, when doing a whole series of patches, getting them in more quickly will help a lot too. Thanks, Marcin [1] https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-te... [2] https://gerrit.ovirt.org/#/c/110304/6/stdci.yaml _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ZYJCKFZ665L...

Hello All. Since we do have centos8 machines now and since we have pretty much moved OST to centos8 do not we miss any leftover that is generating this queue? Or do we still have a lot of unmerged centos8 patches? The problem is that we do not have enough infrastructure to have double capacity on centos7 and centos8, so we will have to aggressively merge all centos8 stuff. I assume most of the load will be on it since 4.4 uses it. Anton. On Thu, Jul 16, 2020 at 11:05 AM Ehud Yonasi <eyonasi(a)redhat.com&gt; wrote: > I see that el7 is not using containers at the moment, probably because of > the el8 support that has been added. > I've sent [1] to enable el7 to utilize containers to reduce the queue. > > [1]: https://gerrit.ovirt.org/110331 > > Regards, > Ehud. > > On Thu, Jul 16, 2020 at 10:30 AM Marcin Sobczyk <msobczyk(a)redhat.com&gt; > wrote: > >> Hi All, >> >> 'check-patch' pipeline for OST has currently a huge queue of jobs to be >> executed, >> some stuck since 14 hrs [1]. When testing patches for OST please >> consider trimming >> down the triggered pipelines like this [2], and marking the patch with >> "WIP" until it's ready. >> Also, when doing a whole series of patches, getting them in more quickly >> will help a lot too. >> >> Thanks, Marcin >> >> [1] >> >> https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-te... >> [2] https://gerrit.ovirt.org/#/c/110304/6/stdci.yaml >> _______________________________________________ >> Devel mailing list -- devel(a)ovirt.org >> To unsubscribe send an email to devel-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ZYJCKFZ665L... >> > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/XKDSMRJQVKR... > -- Anton Marchukov Associate Manager - RHV DevOps - Red Hat