Re: [OE-core] [PATCH v5] libxslt: add ptest support

[Gyorgy Sarvari <skandigraun@gmail.com>]

On 10/28/25 22:05, Pratik Farkase via lists.openembedded.org 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/
> <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 :
>
> For x86-64 : 
> root@qemux86-64:~# ptest-runner libxslt
> START: ptest-runner
> 2025-10-28T20:44
> BEGIN: /usr/lib/libxslt/ptest
> === Running libxslt ptests ===
> FAIL: ./bug-146.xsl (result mismatch)
> failed to stat ./bug-146.err
> FAIL: ./bug-146.xsl (error mismatch)
> ## Running REC2 tests
> ## Running REC tests
> ## Running REC tests (standalone)
> ## Running REC tests without dictionaries
> ## Running REC tests without dictionaries (standalone)
> ## Running general tests
> ## Running general tests without dictionaries
> ## Running encoding tests
> ## Running documents tests
> ## Running numbers tests
> ## Running keys tests
> ## Running namespaces tests
> ## Running extensions tests
> ## Running reports tests
> ## Running exslt common tests
> ## Running exslt date tests
> ## Running exslt dynamic tests
> ## Running exslt functions tests
> ## Running exslt math tests
> ## Running exslt saxon tests
> ## Running exslt sets tests
> ## Running exslt strings tests
> Total 746 tests, 1 errors
> === Finished libxslt ptests ===
> DURATION: 10
> END: /usr/lib/libxslt/ptest
> 2025-10-28T20:44
> STOP: ptest-runner
> TOTAL: 1 FAIL: 0
>
> For arm64: 
> root@qemuarm64:~# ptest-runner libxslt
> START: ptest-runner
> 2025-10-28T20:54
> BEGIN: /usr/lib/libxslt/ptest
> === Running libxslt ptests ===
> Running .libs/runtest
> file ./bug-146.out is 217 bytes, result is 0 bytes
> Result for ./bug-146.xsl failed
> failed to stat ./bug-146.err
> Error for ./bug-146.xsl failed
> File ./bug-146.xsl generated an error
> ## Running REC2 tests
> ## Running REC tests
> ## Running REC tests (standalone)
> ## Running REC tests without dictionaries
> ## Running REC tests without dictionaries (standalone)
> ## Running general tests
> ## Running general tests without dictionaries
> ## Running encoding tests
> ## Running documents tests
> ## Running numbers tests
> ## Running keys tests
> ## Running namespaces tests
> ## Running extensions tests
> ## Running reports tests
> ## Running exslt common tests
> ## Running exslt date tests
> ## Running exslt dynamic tests
> ## Running exslt functions tests
> ## Running exslt math tests
> ## Running exslt saxon tests
> ## Running exslt sets tests
> ## Running exslt strings tests
> Total 746 tests, 1 errors
> FAIL: runtest returned 1
> FAIL: some libxslt tests failed
> Finished libxslt ptests
>
> ERROR: Exit status is 1
> DURATION: 9
> END: /usr/lib/libxslt/ptest
> 2025-10-28T20:54
> STOP: ptest-runner
> TOTAL: 1 FAIL: 1
> Any suggestions on how to proceed or debug further would be appreciated!

It can be reproduced with Mathieu's staging branch (apply your patch on
https://git.openembedded.org/openembedded-core-contrib repo's
mathieu/master-next branch). Not sure if it's due to the new kernel or
something else, haven't looked further.

As a somewhat offtopic, but still related thing:

I noticed the following construct in the run-ptest script:
RT_RET=${PIPESTATUS[0]:-0} || RT_RET=$?

In case the first statement fails, then RT_RET will be always 1. What's
the intention here? If the second part should be a fallback value from
the test execution, then you should store $? before this line, and
assign the stored value to RT_RET.