public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Hemanth.KumarMD@windriver.com
To: openembedded-core@lists.openembedded.org
Subject: Re: [scarthgap][PATCH] glibc: stable 2.39 branch updates
Date: Thu, 05 Feb 2026 21:24:32 -0800	[thread overview]
Message-ID: <554632.1770355472810056681@lists.openembedded.org> (raw)
In-Reply-To: <20260125161623.729884-1-peter.marko@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 386 bytes --]

Hello Peter,

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.

Thanks,
Hemanth

[-- Attachment #2: Type: text/html, Size: 422 bytes --]

  parent reply	other threads:[~2026-02-06  5:24 UTC|newest]

Thread overview: 18+ 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 ` Hemanth.KumarMD [this message]
2026-02-06  6:47   ` [OE-core] [scarthgap][PATCH] " 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
2026-02-06  9:43       ` Yoann Congal
  -- strict thread matches above, loose matches on Subject: below --
2025-10-07  6:31 Deepesh.Varatharajan
2025-07-21 12:23 Deepesh.Varatharajan
2025-05-01  3:03 Deepesh.Varatharajan
2024-11-25  8:01 Deepthi.Hemraj
2024-11-25 16:13 ` Khem Raj
2024-09-29 16:18 Deepesh.Varatharajan
2024-07-19  8:28 Deepthi.Hemraj
2024-05-17 16:22 sundeep.kokkonda
2024-05-17 16:33 ` Sundeep KOKKONDA

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=554632.1770355472810056681@lists.openembedded.org \
    --to=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