Dne 6.5.2017 v 15:08 Sérgio Basto napsal(a):
Hi,
https://copr.fedorainfracloud.org/status/waiting/
107 minutes adrian/ohpc-gcc7-ppc64le 548276 mpi
ch-gnu7-ohpc 3.2-1.ohpc.1.3.1.1 epel-7-ppc64le
97 minutes adrian/ohpc-gcc7-ppc64le 548336 mpic
h-gnu7-ohpc 3.2-1.ohpc.1.3.1.1 epel-7-ppc64le
49 minutes adrian/ohpc-gcc7-ppc64le 548384 ocr-
gnu7-ohpc 1.0.1-1.ohpc.1.3.1.1 epel-7-ppc64le
49 minutes adrian/ohpc-gcc7-ppc64le 548385 ocr-
gnu7-ohpc 1.0.1-1.ohpc.1.3.1.1 epel-7-ppc64le
49 minutes adrian/ohpc-gcc7-ppc64le 548386 ocr-
gnu7-ohpc 1.0.1-1.ohpc.1.3.1.1 epel-7-ppc64le
this kind of use should be limited , seems that is one broken script
not monitored , and other users like me have to wait a long time for
his builds ...
Thnaks
Other users should not be limited by this. We have this setting:
group0_max_workers=40
group0_max_vm_per_user=8
group0_max_vm_total=35
group0_vm_spawn_min_interval=5
group0_max_spawn_processes=5
So one user should occuppy max 8 builders, but there are 32 others available for other
users.
--
Miroslav Suchy, RHCA
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys