Re: Rust reproducibility issue summary

["Sundeep KOKKONDA" <sundeep.kokkonda@windriver.com>]

[-- Attachment #1: Type: text/plain, Size: 2585 bytes --]

Hello,

I've a local reproducer for this issue. Below are a few observations with my analysis.
- The deviation in rustdoc binary are because of the different hash-id generated between the build (as explained above - https://lists.openembedded.org/g/openembedded-core/message/200238)
- The hash-id generates identically when the rust built from it's sources every time.
- During the oe-selftest triggered, when the issue reproduced I can see there are reproducibleA & reproducibleB directories are generated.
But, the rust is not built from sources on both directories beacuse of Setscene Tasks and Shared State. (reproducibleB directory has rust sources built and reproducibleA has setscene realted data copied the files into it from sstate and so, no rust sources are cloned & build into it)
- The above case not always happening with oe-selftest, when the test passed I can see the reproducibleA also has rust sources pulled and built, in this case rustdoc generates identically.
- When the issue reproduced, I did a check on the sstate sigdata to find any deviations but those sig's are identical.
- Also, when the test failed, I tried to find the unique hash-id's generated in rustdoc in the generated rlibs of rust. I could only find one hash-id in rlibs where the rust sources are actually built. The other hash-id not found in rlibs of reproducibleA/B.
- The ' diff .../reproducibleA/tmp/work/core2-64-poky-linux/rust/1.75.0/temp/depsig.do_package_write_deb .../reproducibleB/tmp/work/core2-64-poky-linux/rust/1.75.0/temp/depsig.do_package_write_deb ' shows -
8c8
< -rw-             15932884 6a6618ccfc171ea507ad39eb95bc239116b5f5c9e85a50ce9de3b43c73ff17d7./deploy-debs/core2-64/rust-dbg_1.75.0-r0_amd64.deb
---
> -rw-             15932940 4dcbe007aa8d46e658f95a3651938d67ca5cd55409c503861f365cb9c38f14e7./deploy-debs/core2-64/rust-dbg_1.75.0-r0_amd64.deb
11c11
< -rw-              2902068 564925753476842ea9052311afa27cbc099136113ea9f5394b5554eccb09e8f3./deploy-debs/core2-64/rust-rustdoc_1.75.0-r0_amd64.deb
---
> -rw-              2901612 c0cd05fe344400c0a9d31fecd808c3152481f35dacc0556c006b88a239209358./deploy-debs/core2-64/rust-rustdoc_1.75.0-r0_amd64.deb

I am not sure of what that diff indicates.

Can I get some pointers on -
1. Why only sometimes the setscene setting on reproducibleA (which causes rust sources not to rebuilt)
2. Is there any way/tool to analyze the above depsig data or what is going-on with setscene.

This helps to identify the issue is happening due to sstate? if not I can look into rust.

[-- Attachment #2: Type: text/html, Size: 3834 bytes --]