15528 2024-06-27 13:46:02 +0000 python function code contents in pylibs are not part of the task hash 2024-07-11 15:12:50 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core unspecified x86 Multiple RESOLVED FIXED AB-INT High normal 5.1 M2 1 alexandre.belloni richard.purdie alexandre.belloni meta.mr.watcher meta.watcher randy.macleod richard.purdie tim.orling --- --- No (bug/feature does not impact docs) oldest_to_newest 99269 0 alexandre.belloni 2024-06-27 13:46:02 +0000 RP says: > I believe this causes the following reproducibility failures: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/4998/steps/13/logs/stdio > > https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20240627-3tyeozgn/packages/diff-html/ > This is exposing a problem with the way we're handling python library functions and their effect or lack of effect on the task hashes. If you do something like: bitbake libdrm -S none then look at bitbake-dumpsig tmp/stamps/core2-64-poky-linux/libdrm/2.4.120.do_package.sigdata.* you'll see: List of dependencies for variable oe.package.process_pkgconfig is ['PACKAGES', 'PKGDEST', 'SHLIBSDIRS', 'SHLIBSWORKDIR'] List of dependencies for variable package_do_pkgconfig is ['oe.package.process_pkgconfig'] Variable package_do_pkgconfig value is oe.package.process_pkgconfig(pkgfiles, d) Variable oe.package.process_pkgconfig value is i.e. it knows the function is being used but isn't caching its value. That was by design but it does mean when you change funcitonality, you have to manually tweak the tashhash which I'm not sure is a great idea when put like this. 99370 1 richard.purdie 2024-07-11 15:12:50 +0000 https://git.yoctoproject.org/poky/commit/bitbake?id=0d49931755886d859e2d109eef810f58f98f2cbb https://git.yoctoproject.org/poky/commit/bitbake?id=6be592d2a7268ca394445539f6568d1c64fb0bc7