On Wed, 2016-09-21 at 17:39 +0200, Patrick Ohly wrote:
> new-rmwork-new-scheduler
> elapsed: 42:58.54
> final disk usage: 12873MiB
> max disk usage: 14230MiB
>
> A bit better in terms of max disk usage than with the completion
> scheduler, but not by much. My observation is that in practice there
On Thu, 2016-09-22 at 10:37 -0700, Christopher Larson wrote:
>
> On Thu, Sep 22, 2016 at 5:52 AM, Patrick Ohly
> wrote:
> That's bitbake specific. What I was remembering is something
> generic
> that works for anything that prints test results on
On Thu, Sep 22, 2016 at 5:52 AM, Patrick Ohly
wrote:
> On Wed, 2016-09-21 at 18:08 +0200, Martin Jansa wrote:
> > On Wed, Sep 21, 2016 at 05:39:02PM +0200, Patrick Ohly wrote:
> > > Test script attached. I only ran this once, so I can't vouch that the
> > > numbers are
On Wed, 2016-09-21 at 18:08 +0200, Martin Jansa wrote:
> On Wed, Sep 21, 2016 at 05:39:02PM +0200, Patrick Ohly wrote:
> > Test script attached. I only ran this once, so I can't vouch that the
> > numbers are stable. I remember reading about a benchmark wrapper which
> > can run such a test script
On Wed, Sep 21, 2016 at 05:39:02PM +0200, Patrick Ohly wrote:
> Hello!
>
> rm_work.bbclass currently isn't good enough for use in really tightly
> constrained environments. For example, building core-image-sato with
> 20GB of free disk space should work (final disk usage with rm_work
> active: