Re: [packman] ARM workers idle whereas jobs are waiting...

On Tue, Nov 22, Stefan Botter wrote: > At least swrj01 and swrj03 (my own armv7l workers) are chroot, and are > thus not capable of fulfilling any constraints. This looks like a bug. I have removed the _constraint files like it is done already for the chromium packages, now everything seems to

Re: [packman] ARM workers idle whereas jobs are waiting...

On Mon, 21 Nov 2016 21:19:19 +0100 Olaf Hering wrote: > On Mon, Nov 21, Boris Manojlovic wrote: > > > "kamionche" arm builder has only 2GB of ram so it simply is not > > possible to make it work on it, disk space is not an issue. > > The RAM limit was just for x86, while the

Re: [packman] ARM workers idle whereas jobs are waiting...

"kamionche" arm builder has only 2GB of ram so it simply is not possible to make it work on it, disk space is not an issue. If there is a plan for these higher building packages (higher system requirements that is) to be built i will disable second building process so it will have 2 cpus and real

Re: [packman] ARM workers idle whereas jobs are waiting...

On Mon, 21 Nov 2016 14:38:03 +0100 Guillaume Gardet wrote: > Le 21/11/2016 à 14:33, Guillaume Gardet a écrit : > > Hello, > > > > All ARMv7 workers are idle whereas jobs are waiting... 5 in waiting > > and 329 in blocked. > > > > Why the 5 waitings are not building?

Re: [packman] ARM workers idle whereas jobs are waiting...

Le 21/11/2016 à 14:33, Guillaume Gardet a écrit : Hello, All ARMv7 workers are idle whereas jobs are waiting... 5 in waiting and 329 in blocked. Why the 5 waitings are not building? Maybe the scheduler need a reboot? It seems that all scheduled packages (wxWidgets-3_0-nostl and opencv)

[packman] ARM workers idle whereas jobs are waiting...

Hello, All ARMv7 workers are idle whereas jobs are waiting... 5 in waiting and 329 in blocked. Why the 5 waitings are not building? Maybe the scheduler need a reboot? Guillaume ___ Packman mailing list Packman@links2linux.de