From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <wangmy@fujitsu.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] [OE-core] [PATCH v2] lttng-tools: upgrade 2.14.1 -> 2.15.0
Date: Thu, 09 Apr 2026 14:38:38 +0200 [thread overview]
Message-ID: <DHOMP5U25UXL.ZH8NFSNZYYVM@bootlin.com> (raw)
In-Reply-To: <20260409014036.1519-1-wangmy@fujitsu.com>
On Thu Apr 9, 2026 at 3:40 AM CEST, wangmy via lists.openembedded.org wrote:
> From: Wang Mingyu <wangmy@fujitsu.com>
>
> disable-tests2.patch
> refresshed for 2.15.0
>
> 0001-tests-do-not-strip-a-helper-library.patch
> removed since it's not available in 2.15.0
>
> 0001-common-Autodetect-musl-libc-and-fix-C-compilation-er.patch
> added to fix compile error when enable musl
>
> Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
> ---
Hi Wang,
Thanks for the new version.
Some ptests looks better, but some of these are still failing:
AssertionError:
Failed ptests:
{'lttng-tools': ["tests.serial_78_-_Test_script_'ust/stall-buffer/test_stall_buffer_complex.py'_returned_code_1._0_passed,_0_failed,_0_skipped,_unknown_planned_[total:_0]",
"tests.serial_79_-_Test_script_'ust/stall-buffer/test_stall_buffer_simple.py'_returned_code_1._0_passed,_0_failed,_0_skipped,_unknown_planned_[total:_0]",
"tests.serial_80_-_Test_script_'ust/stall-buffer/test_stall_buffer_timer.py'_returned_code_1._0_passed,_0_failed,_0_skipped,_unknown_planned_[total:_0]"]}
https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/3450
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/3472
Can you have a look at the issue?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-04-09 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 1:40 [PATCH] [OE-core] [PATCH v2] lttng-tools: upgrade 2.14.1 -> 2.15.0 Wang Mingyu
2026-04-09 12:38 ` Mathieu Dubois-Briand [this message]
2026-04-10 10:28 ` Mingyu Wang (Fujitsu)
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=DHOMP5U25UXL.ZH8NFSNZYYVM@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox