On Mon, 2023-12-25 at 08:40 +0000, Richard Purdie via lists.openembedded.org wrote: > On Sun, 2023-12-24 at 23:09 +0000, Alex Kiernan wrote: > > This is the 1.74.1 rust series rebased to include a revert of > > https://github.com/rust-lang/cc-rs/commit/c4f414f449bb7cffba3bc923f277704d1d08a8ec > > which I'm pretty sure is what's causing our filename churn. I've checked > > 1.72.0 and 1.74.1 for the absvdi2.o intrinsic (one of many intrinsics > > which had the issue) and in both cases we're not generating the dirname > > based prefix - hopefully that means that the interim commits are fine > > too, if not we can do the step back through the commits to find the next > > issue. > > > > I've dropped the zvariant tests as upgrading it isn't useful (since it > > no longer includes git crate dependency) and spurious oe-selftest > > failures aren't helpful. I guess we need to include either something > > synthetic which tests git crates, or pull in > > https://github.com/jthornber/thin-provisioning-tools/ from > > meta-openembedded which includes a live example (though who knows for > > how long!) > > > > Assuming this does actually fix the reproducibility issue, I'll look at > > how we fix the issue properly, rather than just reverting the commit > > which I think is our problem, but I'd like to try and get us back on the > > rust release train if we can! > > > > > > Alex Kiernan (6): > > meta-selftest: Drop zvariant recipe > > rust: Upgrade 1.71.1 -> 1.72.0 > > rust: Upgrade 1.72.0 -> 1.72.1 > > rust: Upgrade 1.72.1 -> 1.73.0 > > rust: Upgrade 1.73.0 -> 1.74.0 > > rust: Upgrade 1.74.0 -> 1.74.1 > > Sounds like a good plan, I've started a reproducibility test: > > https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/4142 > > With zvariant, we might be better replacing with a synthetic example > for testing purposes?
That build went green so I ran an a-full to double check and check everything else: https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6374 Curl ptest warning was the only issue (unrelated) so it also looks good. Looks like you might have tracked down the issue, nice work! :) Should I merge this as is or is there something we should do first now we know where the issue is? Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#192904): https://lists.openembedded.org/g/openembedded-core/message/192904 Mute This Topic: https://lists.openembedded.org/mt/103354255/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
