On Fri, 2 Jul 2021 at 13:10, Daniel Gomez <dan...@qtec.com> wrote:
>
> Hi all,
>
> I'm having a problem with perf recipe sstate not being reused in one
> of my 'sstate clients' due to the following difference/change:
>
> pokyuser@da642d39231a:/workdir/build$ bitbake-diffsigs -t perf do_configure
> runtaskdeps changed:
> perf/perf.bb:do_deploy_source_date_epoch with hash
> 5bb942d026e5da1235e70eec6e1568262f9d3efc5f73e73500192308d8ee09a6
> changed to
> perf/perf.bb:do_deploy_source_date_epoch with hash
> 366a660a6f7db7d5222216e8100b50ce8baccc22b0ab8df940a5b721e666994c
> Hash for dependent task perf/perf.bb:do_deploy_source_date_epoch
> changed from 5bb942d026e5da1235e70eec6e1568262f9d3efc5f73e73500192308d8ee09a6
> to 366a660a6f7db7d5222216e8100b50ce8baccc22b0ab8df940a5b721e666994c
I've continued with this issue looking at the task dependencies for
the perf which are the following:
bitbake -g perf
cat task-depends.dot | grep "perf.do_configure\|perf.do_deploy_source"
"perf.do_compile" -> "perf.do_configure"
"perf.do_configure" [label="perf
do_configure\n:1.0-r9\n/workdir/repo/poky/meta/recipes-kernel/perf/perf.bb"]
"perf.do_configure" -> "linux-qtec.do_shared_workdir"
"perf.do_configure" -> "perf.do_deploy_source_date_epoch"
"perf.do_configure" -> "perf.do_patch"
"perf.do_configure" -> "perf.do_prepare_recipe_sysroot"
"perf.do_deploy_source_date_epoch" [label="perf
do_deploy_source_date_epoch\n:1.0-r9\n/workdir/repo/poky/meta/recipes-kernel/perf/perf.bb"]
"perf.do_deploy_source_date_epoch" -> "perf.do_patch"
In my case, both recipes linux-qtec (custom kernel) and perf are not
using the sstate. I have also compared the sigdata for the
linux-qtec.do_shared_workdir task between BUILDA and BUILDB and both
have the same hash:
qt5222-poky-linux/linux-qtec/5.13+gitAUTOINC+e6f9eb0341-r0.do_shared_workdir.1c27b593...
and still they don't reuse the sstate. The rest of the tasks locally
generated in the client have the same hash as the server.
Any idea what can I do/debug next?
>
> Basically, my BUILDA (yocto server) has generated the perf sstate and
> for debugging this error, the sigdata which I have compared with my
> BUILDB (yocto sstate client) figuring out that do_configure task was
> the first one to differ in between builds. According to [1] I should
> see the changes in between builds so I assume in my case it is the
> runtaskdeps but not sure how to proceed now. Comparing the 2 sigdata
> for the do_deploy_source_date_epoch task using bitbake-diffsigs makes
> no output. So, I tried to use bitbake-dumpsig in between them and
> compare the output with diff:
>
> bitbake-dumpsig
> 1.0-r9.do_deploy_source_date_epoch.sigdata.366a660a6f7db7d5222216e8100b50ce8baccc22b0ab8df940a5b721e666994c
> | less > 366.log
> bitbake-dumpsig
> 1.0-r9.do_deploy_source_date_epoch.sigdata.5bb942d026e5da1235e70eec6e1568262f9d3efc5f73e73500192308d8ee09a6
> | less > 5bb.log
> diff -u 366.log 5bb.log
>
> Where you see things like this:
> -List of dependencies for variable libdir is {'baselib', 'exec_prefix'}
> +List of dependencies for variable libdir is {'exec_prefix', 'baselib'}
>
> Or lines being added/removed.
>
> For reference, here the links I've followed:
> [1]
> https://wiki.yoctoproject.org/wiki/TipsAndTricks/Understanding_what_changed_(diffsigs_etc)
> [2]
> https://www.openembedded.org/pipermail/openembedded-core/2014-June/211563.html
>
> Any suggestions on what I should do next to find out what is causing
> the sstate not being reused on the client/consumer of the sstate side?
>
> Thanks in advance,
>
> Daniel
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#153467):
https://lists.openembedded.org/g/openembedded-core/message/153467
Mute This Topic: https://lists.openembedded.org/mt/83937746/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
