On Mon, 2021-10-18 at 09:16 +0200, Jacob Kroon wrote:
> I'm on latest dunfell and using uninative and have put the yocto servers 
> in my SSTATE_MIRRORS:
> 
> my-distro.conf:
> ...
> > SSTATE_MIRRORS ?= "file://.* 
> > http://sstate.yoctoproject.org/3.1.11/PATH;downloadfilename=PATH";
> > require conf/distro/include/yocto-uninative.inc
> > INHERIT += "uninative"
> ...
> 
> but I thought I'd be getting more sstate reuse than I am:
> 
> > bitbake m4-native
> ...
> > Sstate summary: Wanted 12 Found 1 Missed 11 Current 0 (8% match, 0% 
> > complete)
> 
> Is the above reasonable, or should I be able to pull m4-native directly 
> from yocto servers sstate ? If so, is there a way to debug what differs 
> between my local siginfos and the ones on the sstate server ?


In dunfell hash equivalence is enabled and this unfortunately means the sstate
doesn't work very well unless you also have the matching hash equivalence data.

We do now have a way to have a readonly hash equivalence server and we have made
one available from the autobuilder so this data is shared. Unfortunately there
isn't a way to configure dunfell to use one though :(. That patch is a feature
but could be something we consider backporting.

That said, I did a lot of testing/work with master recently as sstate reuse with
hash equivalence was not what we'd expected. We ended up making a lot of
changes, including a bit of a rewrite of the server side of the hash
equivalence. I mention this just to illustrate it isn't a simple problem and
that fixing this in dunfell may be tricky and would need backporting of some
invasive changes. I'm trying to at least get master/honister working right in
the first instance.

Cheers,

Richard







-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157053): 
https://lists.openembedded.org/g/openembedded-core/message/157053
Mute This Topic: https://lists.openembedded.org/mt/86408232/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to