From: Hemanth Kumar M D <Hemanth.KumarMD@windriver.com>
To: Yoann Congal <yoann.congal@smile.fr>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [scarthgap][PATCH] glibc: stable 2.39 branch updates
Date: Fri, 6 Feb 2026 13:49:20 +0530 [thread overview]
Message-ID: <b467cdbc-75d3-4da9-abd6-f5ccdaae4191@windriver.com> (raw)
In-Reply-To: <DG7OEQVVA24V.11T3BEC402DYS@smile.fr>
[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]
On 06-02-2026 12:17 pm, Yoann Congal 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.
>
> Hello,
>
> On Fri Feb 6, 2026 at 6:24 AM CET, Hemanth.KumarMD via lists.openembedded.org wrote:
>> Hello Peter,
> (Yoann here)
>
>> We sometimes see regressions in glibc test runs depending on the local
>> environment. In such cases, it can help to re-trigger the tests to
>> check whether the failures are consistently reproducible. It may also
>> be useful to cross-check the results with autobuilder runs, which
>> generally provide a more stable baseline before concluding on
>> regressions.
> I'm willing to test this on the autobuilder. But I never done that...
> Any pointer? Where do I get the nice test report with the comparison to
> the previous version?
Hello Yoann,
You can trigger a *qemux86-64-tc* build with this patch applied. Once
the build completes, the corresponding results link will be available in
the published artifacts.
example:
https://valkyrie.yocto.io/pub/non-release/20260206-8/testresults/qemux86-64-tc/
The *qemux86-64-tc* build artifacts include the |test-results.json|
file. You can compare this against any recent successful *qemux86-64-tc*
autobuilder run as the baseline.
Hope this helps.
Thanks, Hemanth
>
> Thanks!
> --
> Yoann Congal
> Smile ECS
>
--
Regards,
Hemanth Kumar M D
[-- Attachment #2: Type: text/html, Size: 3018 bytes --]
next prev parent reply other threads:[~2026-02-06 8:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 16:16 [OE-core][scarthgap][PATCH] glibc: stable 2.39 branch updates Peter Marko
2026-02-05 17:08 ` Yoann Congal
2026-02-08 15:18 ` Marko, Peter
2026-02-06 5:24 ` [scarthgap][PATCH] " Hemanth.KumarMD
2026-02-06 6:47 ` [OE-core] " Yoann Congal
2026-02-06 7:42 ` Marko, Peter
2026-02-06 10:19 ` Richard Purdie
2026-02-06 8:19 ` Hemanth Kumar M D [this message]
2026-02-06 9:43 ` Yoann Congal
-- strict thread matches above, loose matches on Subject: below --
2025-10-07 6:31 Deepesh.Varatharajan
2025-10-07 21:30 ` [OE-core] " Khem Raj
2025-10-13 5:43 ` Deepesh Varatharajan
2025-10-13 6:11 ` Khem Raj
2025-07-21 12:23 Deepesh.Varatharajan
2025-07-22 1:38 ` [OE-core] " Khem Raj
2025-06-17 21:11 [OE-core][scarthgap][PATCH] " Peter Marko
2025-05-01 3:03 [scarthgap][PATCH] " Deepesh.Varatharajan
2025-05-01 5:54 ` [OE-core] " Khem Raj
2025-05-02 3:15 ` Deepesh Varatharajan
2025-05-02 3:25 ` Khem Raj
2025-05-02 10:34 ` Randy MacLeod
2025-05-05 4:06 ` Deepesh Varatharajan
2025-02-02 15:52 [OE-core][scarthgap][PATCH] " Peter Marko
2024-09-29 16:18 [scarthgap][PATCH] " Deepesh.Varatharajan
2024-09-29 16:59 ` [OE-core] " Khem Raj
2024-05-17 16:22 sundeep.kokkonda
2024-05-17 16:33 ` Sundeep KOKKONDA
2024-05-17 16:48 ` [OE-core] " Khem Raj
2024-05-17 16:53 ` Marko, Peter
2024-05-17 21:09 ` Steve Sakoman
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=b467cdbc-75d3-4da9-abd6-f5ccdaae4191@windriver.com \
--to=hemanth.kumarmd@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yoann.congal@smile.fr \
/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