https://wiki.koansoftware.com/index.php?action=history&feed=atom&title=Yocto_sstate_usage_summary_to_the_buildYocto sstate usage summary to the build - Revision history2026-04-17T18:03:17ZRevision history for this page on the wikiMediaWiki 1.39.15https://wiki.koansoftware.com/index.php?title=Yocto_sstate_usage_summary_to_the_build&diff=299&oldid=prevKoan: Created page with "== Yocto usage Sstate summary to the build == When building in Yocto Project the user has indication of how much sstate was already present or that would be used by the build..."2021-09-22T16:29:26Z<p>Created page with "== Yocto usage Sstate summary to the build == When building in Yocto Project the user has indication of how much sstate was already present or that would be used by the build..."</p>
<p><b>New page</b></p><div>== Yocto usage Sstate summary to the build ==<br />
<br />
When building in Yocto Project the user has indication of how much sstate was already present<br />
or that would be used by the build thanks to the '''Sstate summary''' message.<br />
<br />
Sstate summary: Wanted 11 Found 11 Missed 0 Current 188 (100% match, 100% complete)<br />
<br />
<br />
<br />
'''Wanted''' is the number of artefacts the build ideally wants from sstate<br />
<br />
'''Found''' is the number of artefacts present in sstate locally or it thinks<br />
are fetchable from any mirrors<br />
<br />
'''Missed''' = Wanted - Found<br />
<br />
'''Current''' is the number of stamps which bitbake viewed as "current", i.e.<br />
it needed to do nothing. Since they're current, it wouldn't bother<br />
querying sstate or considering them any further.<br />
<br />
'''"% match"''' tells you how much of the sstate queried, matched<br />
<br />
'''"% complete"''' tells you how much of the build is already current or<br />
completed<br />
<br />
The reason the current/complete numbers are there are because a build<br />
directory where a build has already partly completed could show a "0%<br />
match" against sstate but its not immediately clear that things which<br />
have already run are never checked for in sstate. A build which was 90%<br />
complete would likely have a high "% match" for a fresh tmpdir so this<br />
was added to try and give people a real idea of how much work remains<br />
in a given build "up front" when you start the build.<br />
<br />
The information is available in the [https://www.yoctoproject.org/docs/current/overview-manual/overview-manual.html#shared-state-cache official manual]<br />
<br />
''Thanks to Richard Purdie for [https://www.openembedded.org/pipermail/openembedded-core/2018-August/272296.html clarifying that].''</div>Koan