From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Pratik Farkase" <pratik.farkase@est.tech>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v5] libxslt: add ptest support
Date: Wed, 29 Oct 2025 12:49:07 +0100 [thread overview]
Message-ID: <DDUS6ZLHP1TA.1RO2V3WLOWZXW@bootlin.com> (raw)
In-Reply-To: <GV2P189MB3005ADB18D1B5A8674AABA72FEFDA@GV2P189MB3005.EURP189.PROD.OUTLOOK.COM>
On Tue Oct 28, 2025 at 10:05 PM CET, Pratik Farkase wrote:
> Hi Mathieu,
>
> I looked at both the Ptest logs you sent and seems like more tests are failing in the autobuilder than in my local QEMU test setup. The failures appear to be byte-level differences (e.g., “230 bytes vs 275 bytes” for bug-147) rather than functional errors.
>
> https://valkyrie.yocto.io/pub/non-release/20251026-107/testresults/qemux86-64-ptest/core-image-ptest-libxslt/
>
> For both qemuarm64 and qemux86-64 machines my local ptest-runner has the following output :
>
Yes, it looks like a bit intermittent. I launched another run both locally
and on the autobuilder, and the result is different: it is closer to
yours.
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/2550
https://valkyrie.yocto.io/pub/non-release/20251029-63/testresults/qemux86-64-ptest/core-image-ptest-libxslt/
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-10-29 11:49 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 ` [OE-core] " Mathieu Dubois-Briand
2025-10-28 21:05 ` Pratik Farkase
2025-10-29 9:23 ` Gyorgy Sarvari
2025-11-03 9:29 ` Pratik Farkase
2025-10-29 11:49 ` Mathieu Dubois-Briand [this message]
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=DDUS6ZLHP1TA.1RO2V3WLOWZXW@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