public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Gyorgy Sarvari <skandigraun@gmail.com>
To: Pratik Farkase <pratik.farkase@est.tech>,
	Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v5] libxslt: add ptest support
Date: Tue, 4 Nov 2025 15:43:16 +0100	[thread overview]
Message-ID: <858bd64d-77fc-40d5-a7d5-800fca2d98e5@gmail.com> (raw)
In-Reply-To: <1874D423590E3BAD.264703@lists.openembedded.org>

On 11/4/25 15:29, Gyorgy Sarvari via lists.openembedded.org wrote:
> On 11/4/25 15:05, Pratik Farkase wrote:
>> Hi Gyorgy,
>>
>> Thanks for your support.
>>
>> I’m now seeing more test failures (as seen in the Autobuilder) when using the `libxml2_2.15.0.bb` recipe from the mathieu/master-next branch, compared to the default `libxml2_2.12.10.bb` recipe from Scarthgap.
>>
>> The ptest implementation for libxslt is identical in both cases, but the number of failing tests increases when we bump the libxml2 version to the one in master. I’m not entirely sure if this is solely due to the version change or if other updates in the newer libxml2 are contributing to the issue.
>>
>> Would you prefer that we wait for the libxslt maintainers to fix these tests upstream, or should I disable the failing tests and roll out a new patch with the existing passing tests in the meantime?
> In the libxslt repo there are 1-2 recent commits that say suspicious
> things like "update test outputs for new libxml2" - if that could be
> checked if they[1][2] fix the problem with new libxml, that would be
> good to know. (I haven't gone further than looking at the recent commit log)
>
> If they are relevant and they fix the issue, then I would remove libxml
> update until it is fixed (it seems there are some other issues with it),

I have to correct myself about the "other issues" statement: I missed
that the problem was present with v2 version of the libxml update, not
with v3. In this case the libxslt tests should pass with the current
libxml (though don't know if it will reach master branch before
Whinlatter release).

> and accept your update in a way that passes all tests with the
> non-updated libxml. And then, once libxml update works, the test-fixing
> patches can be added to libxslt, and everything supposed to work(TM) again.
>
> But on this ML I'm just a random commenter, my personal opinion might
> not be the same as what the project wants :) You might want to wait for
> a second opinion also.
>
> [1]:
> https://gitlab.gnome.org/GNOME/libxslt/-/commit/a7287acdf1dd95e32bde828c10e07949a16b68f3
> [2]:
> https://gitlab.gnome.org/GNOME/libxslt/-/commit/33cd5e56328ab29ef1fd939c4632915e834bb7af
>
>
>> Best Regards,
>> Pratik
>>
>> ________________________________________
>> From: Pratik Farkase <pratik.farkase@est.tech>
>> Sent: 03 November 2025 10:41 AM
>> To: Mathieu Dubois-Briand; Gyorgy Sarvari; openembedded-core@lists.openembedded.org
>> Subject: Re: [OE-core] [PATCH v5] libxslt: add ptest support
>>
>> Hi Mathieu,
>>
>> bug-146 test failure as seen on my local ptest-runner output seems to be fixed and will be incorporated in libxslt master :
>>
>> https://gitlab.gnome.org/GNOME/libxslt/-/issues/159
>>
>> I am not sure why we get different outputs of ptest-runner on Autobuilder and local QEMU test setup. It needs to be investigated further.
>>
>> Best Regards,
>> Pratik
>>
>> ________________________________________
>> From: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
>> Sent: 29 October 2025 12:49 PM
>> To: Pratik Farkase; openembedded-core@lists.openembedded.org
>> Subject: Re: [OE-core] [PATCH v5] libxslt: add ptest support
>>
>> 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
>>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#225724): https://lists.openembedded.org/g/openembedded-core/message/225724
> Mute This Topic: https://lists.openembedded.org/mt/115943432/6084445
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [skandigraun@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>



  parent reply	other threads:[~2025-11-04 14:43 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
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 [this message]
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=858bd64d-77fc-40d5-a7d5-800fca2d98e5@gmail.com \
    --to=skandigraun@gmail.com \
    --cc=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