Shlomi, Can you submit a patch to increase the limit to 6 for (i think all jobs are using the same yaml template) and we'll continue to monitor to queue and see if there is an improvement in the utilization of slaves? E. On Tue, May 10, 2016 at 1:58 PM, David Caro <dcaro@redhat.com> wrote:
On 05/10 13:54, Eyal Edri wrote:
Is there any reason we're limiting the amount of check patch & check merged jobs to run only 3 in parallel?
We had some mess in the past where enabling parallel runs did not really force not using the same slave at the same time, I guess we never reenabled them.
Each jobs runs in mock and on its own VM, anything presenting us from removing this limitation so we won't have idle slaves while other jobs are in the queue?
We can increase it at least to a higher level if we won't one specific job to take over all slaves and starve other jobs, but i think ovirt-engine jobs are probably the biggest consumer of ci, so the threshold should be updated.
+1
-- Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel
phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- David Caro
Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605 Email: dcaro@redhat.com IRC: dcaro|dcaroest@{freenode|oftc|redhat} Web: www.redhat.com RHT Global #: 82-62605
-- Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)