SSTATE MIRRORS only partly working?
Trying my SSTATE_MIRROR test with a recent Poky tree, I find that for the most part, it doesn't work as expected (at least not as I expect).
Here's my test setup:
* Create a complete build
% . /local/poky/oe-init-build-env /local/build_orig % bitbake SOME-RECIPE
* Use that build for the SSTATE_MIRROR
% . /local/poky/oe-init-build-env /local/build_test -- edit conf/local.conf to have these lines:
SSTATE_MIRRORS ?= "\
file://.* file:///local/build_orig/sstate-cache/"
% bitbake SOME-RECIPE
What I find is that this second build is rebuilding a lot of
things, most strikingly the -native packages. Looking into
it, I see that the original build creates
sstate-pseudo-native-i686-linux-1.0-r0-i686-2-999fef0f7f260a6672c3678a831fa36f_populate-sysroot.tgz
but when the test build runs, it's looking for
sstate-pseudo-native-i686-linux-1.0-r0-i686-2-feb469d055bfc4f32074e7e9499eaf22_populate-sysroot.tgz
Odd, but it's not always different, for example
sstate-perl-native-i686-linux-5.12.3-r2-i686-2-75d16ce5b7c945262d819c24f59d1c9f_populate-sysroot.tgz
is the same in both builds and is thus shared.
Note that nothing else has changed, other than the process above. The COREBASE tree is identical/untouched.
Am I missing something here?
Thanks
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 22 lines · Gary Thomas
Trying my
SSTATE_MIRRORtest with a recent Poky tree, I find that for the most part, it doesn't work as expected (at least not as I expect).Here's my test setup:
* Create a complete build
% . /local/poky/oe-init-build-env /local/build_orig % bitbake SOME-RECIPE
* Use that build for theSSTATE_MIRROR
% . /local/poky/oe-init-build-env /local/build_test -- editconf/local.confto have these lines:
SSTATE_MIRRORS?= "\
file://.* file:///local/build_orig/sstate-cache/"
% bitbake SOME-RECIPEWhat I find is that this second build is rebuilding a lot of
things, most strikingly the -native packages. Looking into
it, I see that the original build creates
sstate-pseudo-native-i686-linux-1.0-r0-i686-2-999fef0f7f260a6672c3678a831fa36f_populate-sysroot.tgz
but when the test build runs, it's looking for
sstate-pseudo-native-i686-linux-1.0-r0-i686-2-feb469d055bfc4f32074e7e9499eaf22_populate-sysroot.tgz
Quoted 8 lines
Odd, but it's not always different, for example
sstate-perl-native-i686-linux-5.12.3-r2-i686-2-75d16ce5b7c945262d819c24f59d1c9f_populate-sysroot.tgz
is the same in both builds and is thus shared.Note that nothing else has changed, other than the process above. The COREBASE tree is identical/untouched.
Am I missing something here?
Did you try comparing the siginfo/sigdata files using bitbake-diffsigs?
That should give some clues about what changed.
Cheers,
Richard
Quoted 27 lines · Richard Purdie
Quoted 26 lines · Gary Thomas
Trying my
SSTATE_MIRRORtest with a recent Poky tree, I find that for the most part, it doesn't work as expected (at least not as I expect).Here's my test setup:
* Create a complete build
% . /local/poky/oe-init-build-env /local/build_orig % bitbake SOME-RECIPE
* Use that build for theSSTATE_MIRROR
% . /local/poky/oe-init-build-env /local/build_test -- editconf/local.confto have these lines:
SSTATE_MIRRORS?= "\
file://.* file:///local/build_orig/sstate-cache/"
% bitbake SOME-RECIPEWhat I find is that this second build is rebuilding a lot of things, most strikingly the -native packages. Looking into it, I see that the original build creates
sstate-pseudo-native-i686-linux-1.0-r0-i686-2-999fef0f7f260a6672c3678a831fa36f_populate-sysroot.tgz but when the test build runs, it's looking for sstate-pseudo-native-i686-linux-1.0-r0-i686-2-feb469d055bfc4f32074e7e9499eaf22_populate-sysroot.tgzOdd, but it's not always different, for example
sstate-perl-native-i686-linux-5.12.3-r2-i686-2-75d16ce5b7c945262d819c24f59d1c9f_populate-sysroot.tgzis the same in both builds and is thus shared.
Quoted 8 lines
Quoted 4 lines
Note that nothing else has changed, other than the process above. The COREBASE tree is identical/untouched.
Am I missing something here?
Did you try comparing the siginfo/sigdata files using bitbake-diffsigs?
That should give some clues about what changed.
Odd - I just tried this again after merging up to 31a763d7bd97f57586c6bb9ec223bfa7e333d21c I can't make it happen again - SSTATE_MIRROR is working as I expect. Sadly, I don't have the trees from the previous attempt around any more to diagnose.
My previous merge of f285547a3820f394f7dd9dd974f876353d4ddc6c is when this happened.
I don't see anything obvious that changed between these two revisions that might affect this, but I'm happy it seems to be working again. If it breaks again, I'll know what to look at.
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------