Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sstate always 0% match. #91

Closed
weishan18 opened this issue Sep 29, 2022 · 3 comments
Closed

sstate always 0% match. #91

weishan18 opened this issue Sep 29, 2022 · 3 comments

Comments

@weishan18
Copy link

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
Copy link
Collaborator

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
Copy link

ytan29 commented Nov 15, 2022

@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
Copy link
Contributor

Thanks @ytan29 for your feedback

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants