Re: [OE-core] [PATCH] rust: Drop oeqa-selftest-Increase-timeout-in-process-sigpipe-ru.patch

[Deepesh Varatharajan <deepesh.varatharajan@windriver.com>]

On 11-03-2026 14:44, Alexander Kanavin wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Wed, 11 Mar 2026 at 09:42, Varatharajan, Deepesh via
> lists.openembedded.org
> <deepesh.varatharajan=windriver.com@lists.openembedded.org> 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
Hi Alex,

Thanks for the suggestion.

I will rebase the patch onto the latest sources and resend it. Regarding 
the upstream ticket,
since we don't currently have a recent occurrence of the issue with the 
latest Rust versions,
it may be difficult to open a meaningful report without concrete 
evidence or a reproducible
case. Upstream would likely ask for logs or a reproducible setup.

If the issue appears again with the latest Rust, I’ll make sure to 
collect the necessary
details and open an upstream ticket promptly.

Please let me know if this is fine.

Regards,
Deepesh