Hi Gyorgy, I finished testing libxslt 1.1.43 ptest with both libxml2 2.12.10 and 2.15.0.
Results: - libxml2 2.12.10 + unpatched libxslt → only one remaining failure (bug-146.xsl) - libxml2 2.12.10 + patches [1][2] → 34 test failures. - libxml2 2.15.0 + unpatched libxslt → 34 test failures. - libxml2 2.15.0 + patches [1][2] → only one remaining failure (bug-146.xsl). This confirms that the two upstream commits fix the new-libxml2 (2.15.0) behavior but are not compatible with the current libxml2 2.12.10. So, as you suggested, I’ll keep libxslt 1.1.43 unpatched with libxml2 2.12.10 for now and revisit these patches when libxml2 2.15.0 is updated. Upstream has also acknowledged the remaining bug-146 issue and is preparing a release with the fix (see [3]), but it is not yet merged in master. We wait for the next upstream libxslt release before updating libxml2 and including the test-fixing patches when there are no failures in autobuilder. Thanks for pointing me to the relevant commits — they solve the issue almost entirely. [1] https://gitlab.gnome.org/GNOME/libxslt/-/commit/a7287acdf1dd95e32bde828c10e07949a16b68f3 [2] https://gitlab.gnome.org/GNOME/libxslt/-/commit/33cd5e56328ab29ef1fd939c4632915e834bb7af [3] https://gitlab.gnome.org/GNOME/libxslt/-/issues/159 Best Regards, Pratik ________________________________________ From: Gyorgy Sarvari <[email protected]> Sent: 04 November 2025 3:43 PM To: Pratik Farkase; Mathieu Dubois-Briand; [email protected] Subject: Re: [OE-core] [PATCH v5] libxslt: add ptest support 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 <[email protected]> >> Sent: 03 November 2025 10:41 AM >> To: Mathieu Dubois-Briand; Gyorgy Sarvari; >> [email protected] >> 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 <[email protected]> >> Sent: 29 October 2025 12:49 PM >> To: Pratik Farkase; [email protected] >> 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 (#226128): https://lists.openembedded.org/g/openembedded-core/message/226128 Mute This Topic: https://lists.openembedded.org/mt/115943432/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
