From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Pratik Farkase" <pratik.farkase@est.tech>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v5] libxslt: add ptest support
Date: Mon, 27 Oct 2025 06:56:17 +0100 [thread overview]
Message-ID: <DDSVFR6HJY5J.9F1TJMJY0ZQ0@bootlin.com> (raw)
In-Reply-To: <20251025132107.9296-1-pratik.farkase@est.tech>
On Sat Oct 25, 2025 at 3:21 PM CEST, Pratik Farkase wrote:
> Add ptest support for libxslt 1.1.43 including:
> - do_compile_ptest and do_install_ptest
> - test data installation
> - cleanup of buildpath references
> - added run-ptest installation
>
> Enable --with-plugins only when ptest is enabled, per review feedback.
>
> v3:
> - Remove unconditional --with-plugins (leftover from v2)
>
> v4:
> - adapt run-ptest to emit PASS: or FAIL: lines for each test
> - run-ptest installation with proper permissions
>
> v5:
> - Added FILESEXTRAPATHS using ${BPN} for multilib-safe lookup of run-ptest
> - Guarded run-ptest install in do_install_ptest() to avoid autobuilder failures.
>
> Signed-off-by: Pratik Farkase <pratik.farkase@est.tech>
> ---
Hi Pratik,
Thanks for the new version, but we still have some ptest related errors:
AssertionError:
Failed ptests:
{'libxslt': ['runtest_returned_1', 'some_libxslt_tests_failed']}
https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/2496
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/2535
Ptest logs can be found here:
https://valkyrie.yocto.io/pub/non-release/20251026-107/testresults/qemuarm64-ptest/core-image-ptest-libxslt/
https://valkyrie.yocto.io/pub/non-release/20251026-107/testresults/qemux86-64-ptest/core-image-ptest-libxslt/
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-10-27 5:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 20:31 [PATCH v2] libxslt: add ptest support Pratik Farkase
2025-10-22 20:41 ` [PATCH v3] " Pratik Farkase
2025-10-23 7:16 ` [OE-core] " Gyorgy Sarvari
2025-10-23 7:46 ` Pratik Farkase
2025-10-23 13:59 ` Mathieu Dubois-Briand
2025-10-23 15:34 ` [PATCH v4] " Pratik Farkase
2025-10-25 10:42 ` [OE-core] " Mathieu Dubois-Briand
2025-10-25 13:24 ` Pratik Farkase
2025-10-25 13:21 ` [PATCH v5] " Pratik Farkase
2025-10-27 5:56 ` Mathieu Dubois-Briand [this message]
2025-10-28 21:05 ` [OE-core] " Pratik Farkase
2025-10-29 9:23 ` Gyorgy Sarvari
2025-11-03 9:29 ` Pratik Farkase
2025-10-29 11:49 ` Mathieu Dubois-Briand
2025-11-03 9:41 ` Pratik Farkase
2025-11-04 14:05 ` Pratik Farkase
2025-11-04 14:29 ` Gyorgy Sarvari
[not found] ` <1874D423590E3BAD.264703@lists.openembedded.org>
2025-11-04 14:43 ` Gyorgy Sarvari
2025-11-10 16:48 ` Pratik Farkase
[not found] ` <1876B327C6230E3E.711629@lists.openembedded.org>
2025-11-10 16:51 ` Pratik Farkase
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=DDSVFR6HJY5J.9F1TJMJY0ZQ0@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pratik.farkase@est.tech \
/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