On 3 Aug 2026, at 11:18, Richard Purdie via lists.openembedded.org <[email protected]> wrote: > > On Mon, 2026-08-03 at 11:33 +0200, Pratik Farkase via lists.openembedded.org > wrote: >> The libpng ptest suite consistently times out on qemuriscv64 due to >> the emulated target being too slow to complete all tests within the >> ptest-runner timeout. All individual tests pass but the full suite >> does not finish in time. >> >> [YOCTO #16215] : https://bugzilla.yoctoproject.org/show_bug.cgi?id=16215 >> >> Signed-off-by: Pratik Farkase <[email protected]> >> --- >> meta/conf/distro/include/ptest-packagelists.inc | 4 ++-- >> 1 file changed, 2 insertions(+), 2 deletions(-) > > When you say "does not finish in time", where is the timeout occurring > exactly? > > Do the libpng tests emit output as they go, so each test should reset > the timeout in ptest?
[ ccing Trevor as we’re talking about this on the bug triage call ] I just ran the tests locally on my arm machine. The ptest ran in just over a minute, so a test timeout on a riscv machine would be unexpected. I suggest seeing if you can replicate this interactively, and where the delay is. Is a test hanging, or is a specific test taking forever due to riscv/qemu behaviour, or something else? What might be useful are the .log files in /usr/lib/libpng/ptest/src/tests which will contain the full output of the tests. Ross
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#242951): https://lists.openembedded.org/g/openembedded-core/message/242951 Mute This Topic: https://lists.openembedded.org/mt/120574427/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
