Re: [yocto] PSA for anyone using openSUSE 42.2 (or similar)

2016-12-16 Thread Trevor Woerner
On Fri, Dec 16, 2016 at 12:31 PM, Alexander Kanavin wrote: > Actually, scratch that; if bitbake can detect that the limit is not optimal > at runtime, then it probably should. Direct the bug accordingly. Bitbake can't possibly know how many builds you're going

Re: [yocto] PSA for anyone using openSUSE 42.2 (or similar)

2016-12-16 Thread Trevor Woerner
On Fri, Dec 16, 2016 at 11:06 AM, Alexander Kanavin wrote: > On 12/16/2016 05:06 PM, Trevor Woerner wrote: >> >> I just made this adjustment but given it only happened once or twice a >> week on >> a reasonably busy build machine it might be hard to confirm. I'm

Re: [yocto] PSA for anyone using openSUSE 42.2 (or similar)

2016-12-16 Thread Alexander Kanavin
On 12/16/2016 06:06 PM, Alexander Kanavin wrote: On 12/16/2016 05:06 PM, Trevor Woerner wrote: I just made this adjustment but given it only happened once or twice a week on a reasonably busy build machine it might be hard to confirm. I'm also not sure if setting it to "infinity" is sensible

Re: [yocto] PSA for anyone using openSUSE 42.2 (or similar)

2016-12-16 Thread Alexander Kanavin
On 12/16/2016 05:06 PM, Trevor Woerner wrote: I just made this adjustment but given it only happened once or twice a week on a reasonably busy build machine it might be hard to confirm. I'm also not sure if setting it to "infinity" is sensible ;-) I'm guessing other host distros probably also

[yocto] PSA for anyone using openSUSE 42.2 (or similar)

2016-12-16 Thread Trevor Woerner
Lately I've been seeing very intermittent, sporadic cases where a build will fail with something similar to: fork: Resource temporarily unavailable and nothing else wrong. Simply restarting the build causes it to succeed without incident. I had been seeing this, maybe, twice a week (on a