search

ilbers / isar

Integration System for Automated Root filesystem generation
Other
177 stars 72 forks source link

sstate always 0% match. #91

Closed weishan18 closed 1 year ago

weishan18 commented 1 year ago

I have been trying to reduce the isar build time by enabling sstate. I have copied the sstate_cache folder from isar build and pointing the SSTATE_DIR to the path in local.conf for next build. However, the sstate is always 0% match, and not reducing the build time. Is there any possible reason? I am using latest version Isar.

WiseLord commented 1 year ago

It may be related to absolute paths to the artifacts sstate-cache uses. You could try use different build directories, but fixed sstate-cache location instead.

Also, please use https://groups.google.com/d/forum/isar-users maillist to ask your questions - there are more chances to find a solution for the problems.

ytan29 commented 1 year ago

@WiseLord I'm in the same team with weishan18 where she reported the issue earlier. We forgot to response back to community here. The issue we saw were mainly due to the meta/conf/bitbake.conf has default assignment, and thus the path is being reset unless we use NORMAL assignment at build/local.conf .

ismagulb commented 1 year ago

Thanks @ytan29 for your feedback