Hi,
I have faced a problem today that sstate-cache `${SSTATE_PKG}` generation will
silently fail on the file systems no supporting hard linking.
I've faced this problem on cloud-based Kubernetes cluster, where persistent
volume is mounted to Docker containers as shared sstate-cache location.
Because of https://git.openembedded.org/ openembedded-core/commit/?id=
552197a0c4c9f75a9177c00b197ea9 1296ed9fc4 (
https://git.openembedded.org/openembedded-core/commit/?id=552197a0c4c9f75a9177c00b197ea91296ed9fc4
) change
+ ln $TFILE ${SSTATE_PKG} || true
this will leave sstate folder with only `*...tar.zst.siginfo` files generated,
but no "*...tar.zst"
As a temporary solution, I have replaced it with
+ cp $TFILE ${SSTATE_PKG}
which obviously is not ideal.
What would you suggest?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#170775):
https://lists.openembedded.org/g/openembedded-core/message/170775
Mute This Topic: https://lists.openembedded.org/mt/93712175/21656
Mute
#bitbake:https://lists.openembedded.org/g/openembedded-core/mutehashtag/bitbake
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
