On Wed, 11 Mar 2026 at 09:42, Varatharajan, Deepesh via lists.openembedded.org <[email protected]> wrote: > > There is a bugzilla ticket number in there: > > > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=15625 > > > > and that shows that it did happen on the yocto project autobuilder when > > testing 32 bit PPC. The autobuilder would have been under load and this > > happened in 2024 with this fix around a year ago. > > > > I think Deepesh is right, we should see if upstream would be willing to > > increase the timeout. Carrying patches like this with no hope of ever > > removing them is something we have a natural pressure to try and avoid > > it at all possible. > > Hi Richard, > > How we should proceed further on this? After our discussion, it stayed > in master-next > for a few weeks but has now been removed. Would it be okay if I resend > the patch > after rebasing it to the latest sources? > > If the mentioned failure shows up again, I can open an upstream ticket and > follow up with the community. Please let me know what you suggest.
Yes, please rebase/resend. I would suggest also to open the upstream ticket up front, although upstream might ask for hard evidence that the problem is real, and we don't have any recent/actual evidence. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#232849): https://lists.openembedded.org/g/openembedded-core/message/232849 Mute This Topic: https://lists.openembedded.org/mt/117378407/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
