On Friday, August 26, 2016 6:19:56 PM CEST Michal Novotny wrote:
On Fri, Aug 26, 2016 at 4:50 PM, Pavel Raiskup
<praiskup(a)redhat.com> wrote:
> On Friday, August 26, 2016 4:15:50 PM CEST Michal Novotny wrote:
> > On Fri, Aug 26, 2016 at 3:46 PM, Pavel Raiskup <praiskup(a)redhat.com>
> wrote:
> > > Because in instance I maintain, we have currently like 7 builders
> > > preallocated and booted, and thus backend doesn't have to wait till
the
> > > builder VM boots up.
> >
> > Spawning of virtual machines should/can be independent of copr-backend
> process
> > itself and of allocating worker processes. If that isn't so, that
> > could be a nice improvement.
>
> That already worked -- I don't see benefits in removing that feature (we
> wasted
> a lot of time on it). Just a reason to put "sad face" here.
>
Then I have good news for you...It works now as well! :-) I have just started
a fresh copr-backend instance (remove vms from OS, flush redis, restart
backend) in our dev environment and it immediately began to spawn new
builders.
Does it spawn builders even if there is no build queue yet?
Thanks, Pavel