Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: mathieu.dubois-briand@bootlin.com, raj.khem@gmail.com,
	 openembedded-core@lists.openembedded.org
Cc: Khem Raj <khem.raj@oss.qualcomm.com>
Subject: Re: [OE-core] [PATCH] glibc: Upgrade to 2.44 release
Date: Wed, 29 Jul 2026 07:21:18 +0100	[thread overview]
Message-ID: <9881925e3270e249e1cdc9b8a80110530882ddb7.camel@linuxfoundation.org> (raw)
In-Reply-To: <DKASDKR2N2G5.1R4ZYL1X4YO0C@bootlin.com>

On Wed, 2026-07-29 at 06:56 +0200, Mathieu Dubois-Briand via
lists.openembedded.org wrote:
> Thanks for the upgrade. I can see two failures here: I believe the
> first one is expected, but not the second one.
> 
> So first, buildtools builder is failing with:
> ERROR: Failed to spawn fakeroot worker to run /srv/pokybuild/yocto-
> worker/buildtools/build/layers/openembedded-core/meta/recipes-
> kernel/linux-libc-headers/linux-libc-headers_6.18.bb:do_install:
> [Errno 32] Broken pipe
> 
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/43/builds/4256
> I believe this is just because we need to rebuild uninative on glibc
> upgrade.

That is correct, this one does not block the patch.

> The second issue is a ptest failure:
> Failed ptests:
> {'m4': 'START: ptest-runner\n'
> ...
>        'EAGAIN == EWOULDBLOCK == 11\n'
>        'ENOTSUP == EOPNOTSUPP == 95\n'
>        'PASS: test-errno-h\n'
>        'PASS: test-error.sh\n'
>        'test-execute-main: test-execute-child subprocess failed: No
> such file '
>        'or directory\n'
>        'Timeout! System state:\n'
>        'Collected system state:\n'
>        '+ dmesg\n'
> ...
>        'ERROR: Exited from signal Killed (9)\n'
>        'DURATION: 451\n'}
> 
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/4138
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/4123
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/2009
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/4128
> 
> Can you have a look at that last issue?

I've also seen this in my testing so it does look related and I
isolated to the same patch.

Cheers,

Richard


      reply	other threads:[~2026-07-29  6:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28  7:26 [PATCH] glibc: Upgrade to 2.44 release Khem Raj
2026-07-29  4:56 ` [OE-core] " Mathieu Dubois-Briand
2026-07-29  6:21   ` Richard Purdie [this message]

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=9881925e3270e249e1cdc9b8a80110530882ddb7.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=khem.raj@oss.qualcomm.com \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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