From: Deepesh Varatharajan <deepesh.varatharajan@windriver.com>
To: "Marko, Peter" <Peter.Marko@siemens.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: "Sundeep.Kokkonda@windriver.com" <Sundeep.Kokkonda@windriver.com>,
"Tatrai, Peter" <peter.tatrai.ext@siemens.com>
Subject: Re: [OE-core] [PATCH] rust: Drop oeqa-selftest-Increase-timeout-in-process-sigpipe-ru.patch
Date: Wed, 21 Jan 2026 16:21:45 +0530 [thread overview]
Message-ID: <219a5e65-1619-4f0e-96b5-890556e131f1@windriver.com> (raw)
In-Reply-To: <AS1PR10MB56975E18D333A47C8DA8AC39FD96A@AS1PR10MB5697.EURPRD10.PROD.OUTLOOK.COM>
On 21-01-2026 14:44, Marko, Peter 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.
>
>> -----Original Message-----
>> From: openembedded-core@lists.openembedded.org <openembedded-
>> core@lists.openembedded.org> On Behalf Of Varatharajan, Deepesh via
>> lists.openembedded.org
>> Sent: Wednesday, January 21, 2026 8:55
>> To: openembedded-core@lists.openembedded.org
>> Cc: Sundeep.Kokkonda@windriver.com; Deepesh.Varatharajan@windriver.com
>> Subject: [OE-core] [PATCH] rust: Drop oeqa-selftest-Increase-timeout-in-process-
>> sigpipe-ru.patch
>>
>> From: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
>>
>> This patch was originally added to address a rare failure on the PPC
>> target observed in AB. Currently, we are no longer testing the PPC
>> target in OE-Core. Therefore, we can remove this local patch. We have
>> also verified PPC testing locally several times without this patch,
>> and the issue has not reoccurred.
> Was this tested for 32-bit ppc on a build machine which was under some load?
Yes we did the testing for 32-bit ppc on our local machines and the
issue was not seen.
(In normal load conditions in a shared machine).
> I wouldn't like to play a remove/re-add game, flaky timing tests have tendency to return.
> It's rather trivial patch which should not be causing any maintenance effort.
Agreed. But after the discussion with rust upstream folks in the past,
they have concern about our local
patches. We are working on cleaning up the patches. So, please create an
issue upstream or submit the
patch upstream and backport it.
Regards,
Deepesh
>
> Note that this architecture is not being tested on AB, so the commit message is bit misleading (as it was not observed on Yocto AB).
> Also not being tested in AB is not a good reason to remove something as users are still using it (as a tier-2 feature).
> Note that we're discussing some form of return of Yocto AB testing for 32-bit PPC.
>
> Peter
>
>> 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 d7d44510e4..3edf0899ab 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://revert-link-std-statically-in-rustc_driver-
>> feature.patch;patchdir=${RUSTSRC} \
>> file://0001-riscv32-Define-plain-syscalls-as-their-time64-
>> varian.patch;patchdir=${RUSTSRC} \
>> --
>> 2.49.0
next prev parent reply other threads:[~2026-01-21 10:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 7:54 [PATCH] rust: Drop oeqa-selftest-Increase-timeout-in-process-sigpipe-ru.patch Deepesh.Varatharajan
2026-01-21 9:14 ` [OE-core] " Marko, Peter
2026-01-21 10:51 ` Deepesh Varatharajan [this message]
2026-01-21 10:59 ` Richard Purdie
2026-03-11 8:42 ` Deepesh Varatharajan
2026-03-11 9:14 ` Alexander Kanavin
2026-03-11 9:38 ` Deepesh Varatharajan
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=219a5e65-1619-4f0e-96b5-890556e131f1@windriver.com \
--to=deepesh.varatharajan@windriver.com \
--cc=Peter.Marko@siemens.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.tatrai.ext@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