public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: <Hemanth.KumarMD@windriver.com>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [scarthgap][PATCH] glibc: stable 2.39 branch updates
Date: Fri, 06 Feb 2026 07:47:46 +0100	[thread overview]
Message-ID: <DG7OEQVVA24V.11T3BEC402DYS@smile.fr> (raw)
In-Reply-To: <554632.1770355472810056681@lists.openembedded.org>

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?

Thanks!
-- 
Yoann Congal
Smile ECS



  reply	other threads:[~2026-02-06  6:48 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   ` Yoann Congal [this message]
2026-02-06  7:42     ` [OE-core] " Marko, Peter
2026-02-06 10:19       ` Richard Purdie
2026-02-06  8:19     ` Hemanth Kumar M D
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=DG7OEQVVA24V.11T3BEC402DYS@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=Hemanth.KumarMD@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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