From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <wangmy@fujitsu.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 06/19] hwlatdetect: upgrade 2.8 -> 2.9
Date: Tue, 15 Jul 2025 16:14:27 +0200 [thread overview]
Message-ID: <DBCOWIPUT0N8.ZG0EWT6KR0Y@bootlin.com> (raw)
In-Reply-To: <20250715080819.622-6-wangmy@fujitsu.com>
On Tue Jul 15, 2025 at 10:08 AM CEST, wangmy via lists.openembedded.org wrote:
> From: Wang Mingyu <wangmy@fujitsu.com>
>
> Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
> ---
> meta/recipes-rt/rt-tests/rt-tests.inc | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/meta/recipes-rt/rt-tests/rt-tests.inc b/meta/recipes-rt/rt-tests/rt-tests.inc
> index a2e8558c4c..2042768d5a 100644
> --- a/meta/recipes-rt/rt-tests/rt-tests.inc
> +++ b/meta/recipes-rt/rt-tests/rt-tests.inc
> @@ -1,6 +1,6 @@
> -SRCREV = "f5b910a90b6f5ab0ef6df392e009ffe1429d53af"
> -PV = "2.8"
> +SRCREV = "9166c3f0bb9c5d3e31dc80aff165a5073b5ac5be"
> +PV = "2.9"
> PE = "1"
>
> -SRC_URI = "git://git.kernel.org/pub/scm/utils/rt-tests/rt-tests.git;branch=main;protocol=https"
> +SRC_URI = "git://git.kernel.org/pub/scm/utils/rt-tests/rt-tests.git;branch=main;protocol=https;tag=v${PV}"
>
Hi Wang,
Thanks for the recipe update.
It looks like there is some issue when applying the
0001-sched_attr-Do-not-define-for-glibc-2.41.patch patch after this
update:
ERROR: lib32-rt-tests-1_2.9-r0 do_patch: Applying patch '0001-sched_attr-Do-not-define-for-glibc-2.41.patch' on target directory '/srv/pokybuild/yocto-worker/qemux86-world/build/build/tmp/work/x86-pokymllib32-linux/lib32-rt-tests/2.9/sources/rt-tests-2.9'
...
Hunk #1 FAILED at 42.
Hunk #2 succeeded at 72 with fuzz 2 (offset 4 lines).
1 out of 2 hunks FAILED -- rejects in file src/include/rt-sched.h
https://autobuilder.yoctoproject.org/valkyrie/#/builders/59/builds/2025
Can you fix this build issue please?
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-07-15 14:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 8:08 [OE-core] [PATCH 01/19] debugedit: upgrade 5.1 -> 5.2 Wang Mingyu
2025-07-15 8:08 ` [OE-core] [PATCH 02/19] gi-docgen: upgrade 2025.3 -> 2025.4 Wang Mingyu
2025-07-15 8:08 ` [OE-core] [PATCH 03/19] git: upgrade 2.50.0 -> 2.50.1 Wang Mingyu
2025-07-15 8:08 ` [OE-core] [PATCH 04/19] gnutls: upgrade 3.8.9 -> 3.8.10 Wang Mingyu
2025-07-15 13:10 ` Mathieu Dubois-Briand
2025-07-15 8:08 ` [OE-core] [PATCH 05/19] hwdata: upgrade 0.396 -> 0.397 Wang Mingyu
2025-07-15 8:08 ` [OE-core] [PATCH 06/19] hwlatdetect: upgrade 2.8 -> 2.9 Wang Mingyu
2025-07-15 14:14 ` Mathieu Dubois-Briand [this message]
2025-07-15 8:08 ` [OE-core] [PATCH 07/19] libinput: upgrade 1.28.1 -> 1.28.901 Wang Mingyu
2025-07-15 15:31 ` Alexander Kanavin
2025-07-15 8:08 ` [OE-core] [PATCH 08/19] libsolv: upgrade 0.7.33 -> 0.7.34 Wang Mingyu
2025-07-15 8:08 ` [OE-core] [PATCH 09/19] libwebp: upgrade 1.5.0 -> 1.6.0 Wang Mingyu
2025-07-15 8:08 ` [OE-core] [PATCH 10/19] lsof: upgrade 4.99.4 -> 4.99.5 Wang Mingyu
2025-07-15 8:08 ` [OE-core] [PATCH 11/19] mesa: upgrade 25.1.4 -> 25.1.5 Wang Mingyu
2025-07-15 8:08 ` [OE-core] [PATCH 12/19] ninja: upgrade 1.13.0 -> 1.13.1 Wang Mingyu
2025-07-15 8:08 ` [OE-core] [PATCH 13/19] python3-certifi: upgrade 2025.6.15 -> 2025.7.9 Wang Mingyu
2025-07-15 8:08 ` [OE-core] [PATCH 14/19] python3-hypothesis: upgrade 6.135.16 -> 6.135.29 Wang Mingyu
2025-07-15 8:08 ` [OE-core] [PATCH 15/19] python3-pdm-backend: upgrade 2.4.4 -> 2.4.5 Wang Mingyu
2025-07-15 8:08 ` [OE-core] [PATCH 16/19] taglib: upgrade 2.1 -> 2.1.1 Wang Mingyu
2025-07-15 8:08 ` [OE-core] [PATCH 17/19] tcl: upgrade 9.0.1 -> 9.0.2 Wang Mingyu
2025-07-15 8:08 ` [OE-core] [PATCH 18/19] u-boot: upgrade 2025.04 -> 2025.07 Wang Mingyu
2025-07-15 9:08 ` Gyorgy Sarvari
2025-07-15 14:10 ` Mathieu Dubois-Briand
2025-07-15 8:08 ` [OE-core] [PATCH 19/19] wayland: upgrade 1.23.1 -> 1.24.0 Wang Mingyu
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=DBCOWIPUT0N8.ZG0EWT6KR0Y@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=wangmy@fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.