Re: [OE-core] [PATCH] sstate: Add sstate usage summary to the build

2018-08-27 Thread Richard Purdie
On Mon, 2018-08-27 at 23:47 +0100, richard.pur...@linuxfoundation.org wrote: > On Fri, 2018-08-24 at 23:24 +0200, Martin Jansa wrote: > > This is nice addition, but maybe it would be worth explaining > > somewhere what these numbers actually mean. > > > > e.g. my current build shows: > > Sstate

Re: [OE-core] [PATCH] sstate: Add sstate usage summary to the build

2018-08-27 Thread richard . purdie
On Fri, 2018-08-24 at 23:24 +0200, Martin Jansa wrote: > This is nice addition, but maybe it would be worth explaining > somewhere what these numbers actually mean. > > e.g. my current build shows: > Sstate summary: Wanted 181 Found 39 Missed 142 Current 279 (21% > match, 69% complete) > > From

Re: [OE-core] [PATCH] sstate: Add sstate usage summary to the build

2018-08-24 Thread Martin Jansa
This is nice addition, but maybe it would be worth explaining somewhere what these numbers actually mean. e.g. my current build shows: Sstate summary: Wanted 181 Found 39 Missed 142 Current 279 (21% match, 69% complete) >From quick look at the code my understanding is that: 1) Wanted = Found +

[OE-core] [PATCH] sstate: Add sstate usage summary to the build

2018-08-07 Thread Richard Purdie
Currently the user has no indication of how much sstate was already present or that would be used by the build. This change adds some summary information so that the user can see how much reuse is occurring. To fully work it needs some extra information from a recent bitbake commit but this is