From: Randy MacLeod <randy.macleod@windriver.com>
To: openembedded-core@lists.openembedded.org
Cc: Sundeep.Kokkonda@windriver.com, "Marko,
Peter" <peter.marko@siemens.com>,
Deepesh Varatharajan <deepesh.varatharajan@windriver.com>
Subject: Re: [OE-core] [PATCH v2] rust: Drop oeqa-selftest-Increase-timeout-in-process-sigpipe-ru.patch
Date: Tue, 17 Mar 2026 11:00:41 -0400 [thread overview]
Message-ID: <7974c052-83e6-4725-ae14-62e2d8a202cc@windriver.com> (raw)
In-Reply-To: <8e26998b-52a6-4d5e-964f-5f4b5c09b43c@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 5409 bytes --]
On 2026-03-17 12:10 a.m., Deepesh Varatharajan wrote:
>
> On 17-03-2026 02:38, Randy MacLeod wrote:
>> On 2026-03-11 9:26 a.m., Varatharajan, Deepesh via
>> lists.openembedded.org wrote:
>>> From: Deepesh Varatharajan<Deepesh.Varatharajan@windriver.com>
>>>
>>> This patch was originally introduced to address a rare failure on
>>> the PPC
>>> target and with the latest version of rustc this issue no longer
>>> occurs.
>>> So, this patch can be removed.
>>
>>
>> FYI, merged:
>> 3b5c2d8bdb 2026-03-11 rust: Drop
>> oeqa-selftest-Increase-timeout-in-process-sigpipe-ru.patch
>>
>> If this causes problems for anyone, please let us know and we can
>> consider restoring the patch.
>>
>> Deepesh,
>>
>> Surely there's some existing data that you can point to,
>> to convince upstream to double the timeout if not 10x it?
>>
> Currently I don’t have data since I can’t reproduce the failure with
> the latest rustc.
> If the failure happens again, I’ll collect the data and reach out to
> upstream to discuss
> increasing the timeout.
Deepesh and I talked offline and he reminded me that while we have
some old ppc32 errors logged in the YP bugzilla,
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15625
this issue has NOT happened on the new YP AB HW.
YP AB is not running ppc32 testing anymore so let's wait and see if
anyone else encounters the problem
again and re-opens the bug.
Thanks,
../Randy
>
> Regards,
> Deepesh
>
>> ../Randy
>>
>>> Signed-off-by: Deepesh Varatharajan<Deepesh.Varatharajan@windriver.com>
>>> ---
>>> ...crease-timeout-in-process-sigpipe-ru.patch | 31
>>> -------------------
>>> meta/recipes-devtools/rust/rust-source.inc | 1 -
>>> 2 files changed, 32 deletions(-)
>>> delete mode 100644
>>> meta/recipes-devtools/rust/files/oeqa-selftest-Increase-timeout-in-process-sigpipe-ru.patch
>>>
>>> diff --git
>>> a/meta/recipes-devtools/rust/files/oeqa-selftest-Increase-timeout-in-process-sigpipe-ru.patch
>>> b/meta/recipes-devtools/rust/files/oeqa-selftest-Increase-timeout-in-process-sigpipe-ru.patch
>>>
>>> deleted file mode 100644
>>> index 5bd1abffb4..0000000000
>>> ---
>>> a/meta/recipes-devtools/rust/files/oeqa-selftest-Increase-timeout-in-process-sigpipe-ru.patch
>>> +++ /dev/null
>>> @@ -1,31 +0,0 @@
>>> -From b4524278985f517b0785b6f64a21380dcf1ff096 Mon Sep 17 00:00:00 2001
>>> -From: Peter Tatrai<peter.tatrai.ext@siemens.com>
>>> -Date: Mon, 4 Nov 2024 13:58:16 +0100
>>> -Subject: [PATCH] oeqa/selftest: Increase timeout in process-sigpipe
>>> rust test
>>> -
>>> -This patch increases the timeout for the process-sigpipe rust test,
>>> which
>>> -occasionally fails when the server is under heavy load. Increasing
>>> the timeout
>>> -reduces the likelihood of false negatives under load.
>>> -
>>> -Fixes [YOCTO #15625]
>>> -
>>> -Upstream-Status: Inappropriate [OE testing specific]
>>> -
>>> -Signed-off-by: Peter Tatrai<peter.tatrai.ext@siemens.com>
>>> ----
>>> - tests/ui/process/process-sigpipe.rs | 2 +-
>>> - 1 file changed, 1 insertion(+), 1 deletion(-)
>>> -
>>> -diff --git a/tests/ui/process/process-sigpipe.rs
>>> b/tests/ui/process/process-sigpipe.rs
>>> -index 11f363d62..c12d66016 100644
>>> ---- a/tests/ui/process/process-sigpipe.rs
>>> -+++ b/tests/ui/process/process-sigpipe.rs
>>> -@@ -23,7 +23,7 @@ use std::thread;
>>> - fn main() {
>>> - // Just in case `yes` or `while-echo` doesn't check for EPIPE...
>>> - thread::spawn(|| {
>>> -- thread::sleep_ms(5000);
>>> -+ thread::sleep_ms(50000);
>>> - process::exit(1);
>>> - });
>>> - // QNX Neutrino does not have `yes`. Therefore, use
>>> `while-echo` for `nto`
>>> diff --git a/meta/recipes-devtools/rust/rust-source.inc
>>> b/meta/recipes-devtools/rust/rust-source.inc
>>> index 04204969ba..47a0154cdc 100644
>>> --- a/meta/recipes-devtools/rust/rust-source.inc
>>> +++ b/meta/recipes-devtools/rust/rust-source.inc
>>> @@ -4,7 +4,6 @@ SRC_URI +=
>>> "https://static.rust-lang.org/dist/rustc-${RUST_VERSION}-src.tar.xz;n
>>> file://0001-Define-more-ioctl-codes-on-riscv32gc-unknown-linux-g.patch;patchdir=${RUSTSRC}
>>> \
>>> file://rust-oe-selftest.patch;patchdir=${RUSTSRC} \
>>> file://repro-issue-fix-with-cc-crate-hashmap.patch;patchdir=${RUSTSRC}
>>> \
>>> -file://oeqa-selftest-Increase-timeout-in-process-sigpipe-ru.patch;patchdir=${RUSTSRC}
>>> \
>>> file://0001-src-core-build_steps-tool.rs-switch-off-lto-for-rust.patch;patchdir=${RUSTSRC}
>>> \
>>> file://0001-riscv32-Define-plain-syscalls-as-their-time64-varian.patch;patchdir=${RUSTSRC}
>>> \
>>> file://0001-Update-call-llvm-intrinsics-test.patch;patchdir=${RUSTSRC}
>>> \
>>>
>>> -=-=-=-=-=-=-=-=-=-=-=-
>>> Links: You receive all messages sent to this group.
>>> View/Reply Online
>>> (#232879):https://lists.openembedded.org/g/openembedded-core/message/232879
>>> Mute This Topic:https://lists.openembedded.org/mt/118259934/3616765
>>> Group Owner:openembedded-core+owner@lists.openembedded.org
>>> Unsubscribe:https://lists.openembedded.org/g/openembedded-core/unsub
>>> [randy.macleod@windriver.com]
>>> -=-=-=-=-=-=-=-=-=-=-=-
>>>
>>
>> --
>> # Randy MacLeod
>> # Wind River Linux
--
# Randy MacLeod
# Wind River Linux
[-- Attachment #2: Type: text/html, Size: 10653 bytes --]
prev parent reply other threads:[~2026-03-17 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 13:26 [PATCH v2] rust: Drop oeqa-selftest-Increase-timeout-in-process-sigpipe-ru.patch Deepesh.Varatharajan
2026-03-16 21:08 ` [OE-core] " Randy MacLeod
2026-03-17 4:10 ` Deepesh Varatharajan
2026-03-17 15:00 ` Randy MacLeod [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7974c052-83e6-4725-ae14-62e2d8a202cc@windriver.com \
--to=randy.macleod@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=deepesh.varatharajan@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.marko@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox