> On Thu, 14 Sept 2023 at 21:54, Richard Purdie > <richard.pur...@linuxfoundation.org> wrote: > > The tools are already supposed to support doing this with local file > > sstate sources, they just do a bad job at getting the diffs right. One > > intent of this work item was to try and understand why they don't work > > and address that so at least for filesystem sstate mirrors, you can > > get better results. I don't know how we solve the remote http issue as yet. > > I ran a few experiments with bitbake -S printdiff, and so far I haven't yet > seen > an unhelpful result. Here's the most impressive one: > > $ bitbake libsolv-native (uses cmake-native) $ git revert <latest cmake > version > update> $ rm -rf build/tmp/ $ bitbake -S printdiff libsolv-native ... > The differences between the current build and any cached tasks start at the > following tasks: > /srv/work/alex/poky/meta/recipes-devtools/cmake/cmake- > native_3.27.4.bb:do_recipe_qa > NOTE: Writing task signature files > Writing locked sigs to /srv/storage/alex/yocto/build-sstate/locked-sigs.inc > > Task cmake-native:do_recipe_qa couldn't be used from the cache because: > We need hash > 5e649a49c4f0de2e62bc8fa4215df1021b9772762065352ef0d204d2d72f4efb, > closest matching task was > 85c73eadca06d0e92fcea130ae6e23e902c96314ef1c38c60a14ed3445d24ed7 > basehash changed from > 7d4adf817d99893a30a94330803a0eb1c00652ab217c21599944f81f023af6cd to > 7e93631376ed159c11460647bf7f4178cb260d44f367d0858c2cd96ae2256b09 > Variable PV value changed from '3.27.5' to '3.27.4' > Variable SRC_URI[sha256sum] value changed from > '5175e8fe1ca9b1dd09090130db7201968bcce1595971ff9e9998c2f0765004c9' > to > '0a905ca8635ca81aa152e123bdde7e54cbe764fdd9a70d62af44cad8b92967af' > > That's pretty good, isn't it? It does print both what needs to be re-run, and > *why* as well. > > I have no idea yet what kind of magic it does to find the 'closest matching > task' > in sstate, but if this breaks down in some other scenarios, we need to find > them > to get a starting point for making the tools better. Ideas? I'm ready to try > them > :)
That is very impressive and I'd also love to hear about what heuristics it uses. We use Artifactory to host our sstate. (Artifactory doesn’t have specific support for it, it's just basically acting as a generic HTTP server. But it makes things like LDAP easy). I have for a while been thinking of building a tool that tries to find the "closest" sstate on the server and then recursively runs bitbake-diffsig on it. The tool was going to be called 'why-not-sstate'. Thanks, Chris
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#188008): https://lists.openembedded.org/g/openembedded-core/message/188008 Mute This Topic: https://lists.openembedded.org/mt/101501384/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
