public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <alex.kanavin@gmail.com>, <openembedded-core@lists.openembedded.org>
Cc: "Alexander Kanavin" <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH] libnl: upgrade 3.11.0 -> 3.12.0
Date: Tue, 30 Dec 2025 15:54:05 +0100	[thread overview]
Message-ID: <DFBMYE2AZW0G.2OICW0SD4EGBV@bootlin.com> (raw)
In-Reply-To: <20251229124538.1535197-1-alex.kanavin@gmail.com>

On Mon Dec 29, 2025 at 1:45 PM CET, Alexander Kanavin via lists.openembedded.org wrote:
> From: Alexander Kanavin <alex@linutronix.de>
>
> Remove a patch as the issue has been fixed upstream.
>
> Backport a couple patches to address ptest issues due to missing
> kernel modules (they're not built in standard linux-yocto):
> https://github.com/thom311/libnl/issues/448
>
> Signed-off-by: Alexander Kanavin <alex@linutronix.de>
> ---

Hi Alexander,

Just some note: it looks like some ptest is failing intermittently on
ARM64 after this upgrade. I'm not sure how bad the whole situation is,
but it's bad enough that I already saw it fail twice today:

Failed ptests:
{'libnl': ['nl-test-util.c:Core:route_1_The_list_of_2_routes_did_not_find_a_one-to-one_match_with_the_list_of_3_expected_routes']}

https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/2800
https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/2802

Yet on both times, the rebuild succeed. No issues on other
architectures.

I will keep the patch in my branch, so I will try to monitor the failure
frequency.

Thanks,
Mathieu

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



  reply	other threads:[~2025-12-30 14:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-29 12:45 [PATCH] libnl: upgrade 3.11.0 -> 3.12.0 Alexander Kanavin
2025-12-30 14:54 ` Mathieu Dubois-Briand [this message]
2026-01-02 11:58   ` [OE-core] " Alexander Kanavin
2026-01-05  8:36     ` Mathieu Dubois-Briand

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=DFBMYE2AZW0G.2OICW0SD4EGBV@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=alex.kanavin@gmail.com \
    --cc=alex@linutronix.de \
    --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