public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <Hemanth.KumarMD@windriver.com>,
	<openembedded-core@lists.openembedded.org>
Cc: <Sundeep.Kokkonda@windriver.com>, <Randy.MacLeod@windriver.com>
Subject: Re: [OE-core] [PATCH v2 2/7] gettext: Upgrade 0.26 -> 1.0
Date: Mon, 09 Mar 2026 07:56:07 +0100	[thread overview]
Message-ID: <DGY200N2IVAT.31AXPCZZ9K6JG@bootlin.com> (raw)
In-Reply-To: <20260308150834.2508331-2-Hemanth.KumarMD@windriver.com>

On Sun Mar 8, 2026 at 4:07 PM CET, Hemanth Kumar M D via lists.openembedded.org wrote:
> From: Randy MacLeod <Randy.MacLeod@windriver.com>
>
> Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
> Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
> ---

Hi Hemanth, Randy,

Thanks for the upgrade.

We have some ptest failures here:

Failed ptests:
{'gettext': ['autopoint-1', 'autopoint-2']}


https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/1202
https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/3207
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/3237

Ptest logs can be found here:

https://valkyrie.yocto.io/pub/non-release/20260308-104/testresults/qemuriscv64-ptest/core-image-ptest-gettext/
https://valkyrie.yocto.io/pub/non-release/20260308-104/testresults/qemuarm64-ptest/core-image-ptest-gettext/
https://valkyrie.yocto.io/pub/non-release/20260308-104/testresults/qemux86-64-ptest/core-image-ptest-gettext/

Can you have a look at these?

In some of these logs, I can also see some failures related to glib-2.0.

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2026-03-09  6:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-08 15:07 [PATCH v2 1/7] glibc: Upgrade to 2.43 release Hemanth.KumarMD
2026-03-08 15:07 ` [PATCH v2 2/7] gettext: Upgrade 0.26 -> 1.0 Hemanth.KumarMD
2026-03-09  6:56   ` Mathieu Dubois-Briand [this message]
2026-03-09 14:50     ` [OE-core] " Randy MacLeod
2026-03-08 15:07 ` [PATCH v2 3/7] pseudo: fix for build with glibc-2.43 Hemanth.KumarMD
2026-03-08 16:37   ` [OE-core] " Martin Jansa
2026-04-07  8:54     ` Böszörményi Zoltán
     [not found]     ` <18A40738790ACBCC.657799@lists.openembedded.org>
2026-04-07 11:39       ` Böszörményi Zoltán
2026-04-07 14:08         ` Martin Jansa
2026-04-07 15:21           ` Böszörményi Zoltán
     [not found]           ` <18A41C5827F22307.777565@lists.openembedded.org>
2026-04-07 15:38             ` Böszörményi Zoltán
2026-04-08  9:44               ` Paul Barker
2026-03-08 15:07 ` [PATCH v2 4/7] gcc-runtime: avoid discarded-qualifiers build failure with glibc 2.43 Hemanth.KumarMD
2026-03-08 15:07 ` [PATCH v2 5/7] libxcrypt: " Hemanth.KumarMD
2026-03-08 15:07 ` [PATCH v2 6/7] barebox-tools: fix " Hemanth.KumarMD
2026-03-08 15:07 ` [PATCH v2 7/7] ltp: workaround openat2 " Hemanth.KumarMD
2026-03-08 16:58   ` [OE-core] " Mathieu Dubois-Briand
2026-03-09  7:13 ` [OE-core] [PATCH v2 1/7] glibc: Upgrade to 2.43 release Mathieu Dubois-Briand
2026-03-09 13:26   ` Sundeep KOKKONDA
2026-03-09 13:54     ` Richard Purdie

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=DGY200N2IVAT.31AXPCZZ9K6JG@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=Hemanth.KumarMD@windriver.com \
    --cc=Randy.MacLeod@windriver.com \
    --cc=Sundeep.Kokkonda@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