From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <bin.lan.cn@windriver.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH v5 0/1] babeltrace2: upgrade 2.0.6 -> 2.1.0
Date: Thu, 13 Mar 2025 18:59:31 +0100 [thread overview]
Message-ID: <D8FC1AEI4MBQ.2COAWNC1NGIQE@bootlin.com> (raw)
In-Reply-To: <20250313021751.2313822-1-bin.lan.cn@windriver.com>
On Thu Mar 13, 2025 at 3:17 AM CET, Bin Lan via lists.openembedded.org wrote:
> From: Bin Lan <bin.lan.cn@windriver.com>
>
> v3:
> Some failed test cases are disabled.
> All test cases are passed when running in intel-x86-64 board.
>
> v4:
> The Upstream-Status of patches is set to Pending, I will discuss it with Babeltrace2 project.
> Add some notes in the commit log to explain the license change significantly.
> Add more notes in the commit message to explain the change of babeltrace2_2.1.0.bb.
> Remove "INSANE_SKIP:${PN}-ptest += "buildpaths" in this patch by setting the correct environment variables in env.sh.
> All test cases are passed when running in intel-x86-64 board.
>
> v5:
> 0001-Make-manpages-multilib-identical.patch and 0001-tests-set-the-correct-plugin-directory.patch
> are submitted to Babeltrace project.
> All test cases (no skipped test cases) are passed when running in intel-x86-64
> and qemux86-64 as the following shown:
>
> Testsuite summary for babeltrace2 2.1.0
> # TOTAL: 2022
> # PASS: 2022
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 0
> # XPASS: 0
> # ERROR: 0
>
> Bin Lan (1):
> babeltrace2: upgrade 2.0.6 -> 2.1.0
>
> ...001-Make-manpages-multilib-identical.patch | 12 +-
> ...not-run-test-applications-from-.libs.patch | 28 ----
> ...-fix-test-applications-in-cpp-common.patch | 129 ++++++++++++++++++
> ...sts-set-the-correct-plugin-directory.patch | 30 ++++
> .../lttng/babeltrace2/run-ptest | 4 +-
> ...eltrace2_2.0.6.bb => babeltrace2_2.1.0.bb} | 35 ++++-
> 6 files changed, 198 insertions(+), 40 deletions(-)
> delete mode 100644 meta/recipes-kernel/lttng/babeltrace2/0001-tests-do-not-run-test-applications-from-.libs.patch
> create mode 100644 meta/recipes-kernel/lttng/babeltrace2/0001-tests-fix-test-applications-in-cpp-common.patch
> create mode 100644 meta/recipes-kernel/lttng/babeltrace2/0001-tests-set-the-correct-plugin-directory.patch
> rename meta/recipes-kernel/lttng/{babeltrace2_2.0.6.bb => babeltrace2_2.1.0.bb} (69%)
Hi,
Thanks for the new version, but I believe we do have some failing
ptests:
https://autobuilder.yoctoproject.org/valkyrie/api/v2/logs/1758114/raw_inline
Can you have a look at those please?
More details can be found in:
https://valkyrie.yocto.io/pub/non-release/20250313-87/testresults/qemux86-64-ptest/core-image-ptest-babeltrace2/
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-03-13 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 2:17 [OE-core][PATCH v5 0/1] babeltrace2: upgrade 2.0.6 -> 2.1.0 bin.lan.cn
2025-03-13 2:17 ` [OE-core][PATCH v5 1/1] " bin.lan.cn
2025-03-13 17:59 ` Mathieu Dubois-Briand [this message]
2025-03-14 8:26 ` [OE-core][PATCH v5 0/1] " Bin Lan
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=D8FC1AEI4MBQ.2COAWNC1NGIQE@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=bin.lan.cn@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;
as well as URLs for NNTP newsgroup(s).