From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: pratik.farkase@est.tech, openembedded-core@lists.openembedded.org
Cc: pratik.farkase@ericsson.com
Subject: Re: [OE-core][PATCH v1] libpng: ptest: disable for riscv64 due to timeout
Date: Mon, 03 Aug 2026 11:18:38 +0100 [thread overview]
Message-ID: <30940d7e4b46c8b44c0921956fb0785b4d164606.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260803093344.15211-1-pratik.farkase@est.tech>
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 <pratik.farkase@est.tech>
> ---
> 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?
Or are the individual tests really so slow that they don't emit any
output within ptest's timeout?
We did have an issue a while back there the output wasn't being flushed
periodically and once we did that, we stopped hitting the timeouts,
hence the questions.
I'd just like to understand where the issue is before we disable it
entirely. A comment about why it was disabled might also be helpful if
we do ever come to revisit this.
Cheers,
Richard
next prev parent reply other threads:[~2026-08-03 10:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 9:33 [OE-core][PATCH v1] libpng: ptest: disable for riscv64 due to timeout Pratik Farkase
2026-08-03 10:18 ` Richard Purdie [this message]
2026-08-06 15:07 ` Ross Burton
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=30940d7e4b46c8b44c0921956fb0785b4d164606.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=pratik.farkase@ericsson.com \
--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