[opensuse-buildservice] scheduled packages are not build
for ages, while there are plenty idle workers at the moment?! E.g. the virtualbox packages here: https://build.opensuse.org/project/monitor/home:frispete:Kernel-current Due to the update to 4.8.2, BS built the kernel packages yesterday, but the virtualbox packages are kept in scheduling state since then. OTOH, 500 workers are idle now. Any idea, why it behaves like this? TIA, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Okt 18 2016, Hans-Peter Jansen <hpj@urpla.net> wrote:
for ages, while there are plenty idle workers at the moment?!
E.g. the virtualbox packages here:
https://build.opensuse.org/project/monitor/home:frispete:Kernel-current
Due to the update to 4.8.2, BS built the kernel packages yesterday, but the virtualbox packages are kept in scheduling state since then.
OTOH, 500 workers are idle now.
Any idea, why it behaves like this?
None of the idle workers fulfill the constraints. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Dienstag, 18. Oktober 2016, 10:00:20 CEST wrote Hans-Peter Jansen:
for ages, while there are plenty idle workers at the moment?!
E.g. the virtualbox packages here:
https://build.opensuse.org/project/monitor/home:frispete:Kernel-current
Due to the update to 4.8.2, BS built the kernel packages yesterday, but the virtualbox packages are kept in scheduling state since then.
OTOH, 500 workers are idle now.
Any idea, why it behaves like this?
You require a build system with 14GB memory. Seems we do not offer that atm. Btw, we are currently working on a feature to make such mistakes more visible ... # eosc cat home:frispete:Kernel-current virtualbox _constraints ... <constraints> <hardware> <physicalmemory> <size unit="M">14000</size> </physicalmemory> </hardware> </constraints>
TIA, Pete
-- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hi Adrian, On Dienstag, 18. Oktober 2016 10:30:15 Adrian Schröter wrote:
On Dienstag, 18. Oktober 2016, 10:00:20 CEST wrote Hans-Peter Jansen:
for ages, while there are plenty idle workers at the moment?!
E.g. the virtualbox packages here:
https://build.opensuse.org/project/monitor/home:frispete:Kernel-current
Due to the update to 4.8.2, BS built the kernel packages yesterday, but the virtualbox packages are kept in scheduling state since then.
OTOH, 500 workers are idle now.
Any idea, why it behaves like this?
You require a build system with 14GB memory. Seems we do not offer that atm. Btw, we are currently working on a feature to make such mistakes more visible ...
# eosc cat home:frispete:Kernel-current virtualbox _constraints ... <constraints> <hardware> <physicalmemory> <size unit="M">14000</size> </physicalmemory> </hardware> </constraints>
Thank you for enlightment. Obviously, my package inherited that from Virtualization virtualbox, where Larry changed this constraint 5 days ago. Cheers, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 10/18/2016 04:45 AM, Hans-Peter Jansen wrote:
Hi Adrian,
On Dienstag, 18. Oktober 2016 10:30:15 Adrian Schröter wrote:
On Dienstag, 18. Oktober 2016, 10:00:20 CEST wrote Hans-Peter Jansen:
for ages, while there are plenty idle workers at the moment?!
E.g. the virtualbox packages here:
https://build.opensuse.org/project/monitor/home:frispete:Kernel-current
Due to the update to 4.8.2, BS built the kernel packages yesterday, but the virtualbox packages are kept in scheduling state since then.
OTOH, 500 workers are idle now.
Any idea, why it behaves like this?
You require a build system with 14GB memory. Seems we do not offer that atm. Btw, we are currently working on a feature to make such mistakes more visible ...
# eosc cat home:frispete:Kernel-current virtualbox _constraints ... <constraints> <hardware> <physicalmemory> <size unit="M">14000</size> </physicalmemory> </hardware> </constraints>
Thank you for enlightment. Obviously, my package inherited that from Virtualization virtualbox, where Larry changed this constraint 5 days ago.
That requirement changed to prevent packages from crashing by running out of memory on OBS even though the osc builds are successful on my own machine with 8 GB of RAM. Note that these builds DID NOT use any swap. Larry -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hi Larry, On Dienstag, 18. Oktober 2016 09:32:29 Larry Finger wrote:
On 10/18/2016 04:45 AM, Hans-Peter Jansen wrote:
On Dienstag, 18. Oktober 2016 10:30:15 Adrian Schröter wrote:
You require a build system with 14GB memory. Seems we do not offer that atm. Btw, we are currently working on a feature to make such mistakes more visible ...
Thank you for enlightment. Obviously, my package inherited that from Virtualization virtualbox, where Larry changed this constraint 5 days ago.
That requirement changed to prevent packages from crashing by running out of memory on OBS even though the osc builds are successful on my own machine with 8 GB of RAM. Note that these builds DID NOT use any swap.
I love those behavioral differences, sure you, too... ;) 12M looks like a decent value - thanks. For the record, which processes were crashing? if it's gcc, we should limit _smp_mflags, since that typically translates to -j16 on the BS, and this may result in such pathological situations for virtualbox. Cheers, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 10/18/2016 10:22 AM, Hans-Peter Jansen wrote:
Hi Larry,
On Dienstag, 18. Oktober 2016 09:32:29 Larry Finger wrote:
On 10/18/2016 04:45 AM, Hans-Peter Jansen wrote:
On Dienstag, 18. Oktober 2016 10:30:15 Adrian Schröter wrote:
You require a build system with 14GB memory. Seems we do not offer that atm. Btw, we are currently working on a feature to make such mistakes more visible ...
Thank you for enlightment. Obviously, my package inherited that from Virtualization virtualbox, where Larry changed this constraint 5 days ago.
That requirement changed to prevent packages from crashing by running out of memory on OBS even though the osc builds are successful on my own machine with 8 GB of RAM. Note that these builds DID NOT use any swap.
I love those behavioral differences, sure you, too... ;) 12M looks like a decent value - thanks.
For the record, which processes were crashing? if it's gcc, we should limit _smp_mflags, since that typically translates to -j16 on the BS, and this may result in such pathological situations for virtualbox.
The crashing process is g++ while compiling the webserv part of the package. The make step is already limited to -j2, which helped the build, but 8 MB was still not enough - 12 MB seems to work. but we will need more testing. Larry -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On mardi, 18 octobre 2016 20.17:21 h CEST Larry Finger wrote:
On 10/18/2016 10:22 AM, Hans-Peter Jansen wrote:
Hi Larry,
On Dienstag, 18. Oktober 2016 09:32:29 Larry Finger wrote:
On 10/18/2016 04:45 AM, Hans-Peter Jansen wrote:
On Dienstag, 18. Oktober 2016 10:30:15 Adrian Schröter wrote:
You require a build system with 14GB memory. Seems we do not offer that atm. Btw, we are currently working on a feature to make such mistakes more visible ...
Thank you for enlightment. Obviously, my package inherited that from Virtualization virtualbox, where Larry changed this constraint 5 days ago.
That requirement changed to prevent packages from crashing by running out of memory on OBS even though the osc builds are successful on my own machine with 8 GB of RAM. Note that these builds DID NOT use any swap.
I love those behavioral differences, sure you, too... ;) 12M looks like a decent value - thanks.
For the record, which processes were crashing? if it's gcc, we should limit _smp_mflags, since that typically translates to -j16 on the BS, and this may result in such pathological situations for virtualbox.
The crashing process is g++ while compiling the webserv part of the package. The make step is already limited to -j2, which helped the build, but 8 MB was still not enough - 12 MB seems to work. but we will need more testing.
Larry
I sed /MB/GB/ no ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (5)
-
Adrian Schröter -
Andreas Schwab -
Bruno Friedmann -
Hans-Peter Jansen -
Larry Finger