On Wed, 2024-04-17 at 11:36 +0000, Ross Burton via lists.yoctoproject.org wrote: > On 17 Apr 2024, at 09:50, Richard Purdie via lists.yoctoproject.org > <[email protected]> wrote: > > For b), updating buildtools should resolve it, I thought I had done > > that but there were a lot of moving pieces so I must not have got > > the > > latest. > > > > I'm proposing we do but this into QA as I'd not block release on > > these > > issues. I've done my best to get this into as good a shape as we > > can. > > Agreed. Can we do a build in the meantime of the specific job that > failed so we can verify the buildtools/pip issue is resolved?
I dug into the "github failure" and it turns out that if you have git 2.44.0 compiled/linked against curl 8.7.1 then the command: git-clone --bare --mirror https://github.com/grpc/grpc.git /tmp/somewhere exits silently with an error exit code of 141 (SIGPIPE). With curl 8.6.0 this doesn't happen and the new buildtools has the new curl+git version. You can demo this in a build quite simply with: $ bitbake git-replacement-native -c compile then: $ PATH=./tmp/work/aarch64-linux/git-native/2.44.0/git-2.44.0/:$PATH git-clone --bare --mirror https://github.com/grpc/grpc.git /tmp/bitbake-fetch-test More digging to do to debug it but that should be enough to let others reproduce. I suspect it will happen on x86 too, I just used the arm worker to narrow it down since it was the most frequent occurrence. You have to manipulate PATH so git's internal exec calls find the right git binaries. We'll not mention how it took me to work that out. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#62954): https://lists.yoctoproject.org/g/yocto/message/62954 Mute This Topic: https://lists.yoctoproject.org/mt/105575131/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
