Open DaniilKl opened 1 week ago
@PLangowski , @m-iwanicki, feel free to add some ideas here.
@DaniilKl Maybe because cache.dasharo.com
contains only sstate from main branch. I checked couple random dependencies and in all cases cache contained older versions e.g.
./6a/08/sstate:sqlite3-native::3.38.5:r0::10
(cache) and ./8a/ef/sstate:sqlite3-native::3.45.1:r0::12
(local).
It happened most likely because main is compatible with honister
and kirkstone
while develop is compatible with scarthgap
. Usually there are a lot of changes to a lot of recipes/dependencies when changing Yocto version and there is 2 year gap between release of Kirkstone
and Scarthgap
I see. Additionally there are fails in actions
in meta-dts
due to changes in our infrastructure.
So what do we need here to solve this issue? Should we host both master and develop caches? That sounds reasonable to me.
Sounds ok. I left this issue open, because we are going to make some changes in our infrastructure, and this issue will serve as a reminder.
Tried building from master now, no cache was reused. Something is off.
Component
Dasharo Tools Suite
Device
other
Dasharo version
-
Dasharo Tools Suite version
22840b7e4e1199952bb04f8aa0760531998793e3
Brief summary
No cache is being used during build
How reproducible
100%
How to reproduce
BUild
meta-dts
on commit22840b7e4e1199952bb04f8aa0760531998793e3
:Expected behavior
At least small part of cache from
cache.dasharo.com
is being used.Actual behavior
No cache is being used and build starts from zero.
Screenshots
Additional context
The problem seems to be connected with branch
pre-commit
cos it have appeared just after merging the branch intodevelop
.Solutions you've tried
No response