From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Pratik Farkase" <pratik.farkase@est.tech>,
<openembedded-core@lists.openembedded.org>
Cc: <pratik.farkase@ericsson.com>
Subject: Re: [OE-core][PATCH v3] libsoup: add ptest support
Date: Fri, 16 Oct 2026 10:05:35 +0200 [thread overview]
Message-ID: <DM63VLOX4BUM.15QP91UQU5UL6@bootlin.com> (raw)
In-Reply-To: <20261014120737.24575-1-pratik.farkase@est.tech>
On Wed Oct 14, 2026 at 2:07 PM CEST, Pratik Farkase wrote:
> Build the installed-tests via the meson tests/installed_tests options
> (enabled through a new 'tests' PACKAGECONFIG when ptest is in
> DISTRO_FEATURES) and run them under ptest with
> gnome-desktop-testing-runner.
>
> Tested on qemux86-64 with ptest-runner.
>
> Signed-off-by: Pratik Farkase <pratik.farkase@est.tech>
> ---
Hi Pratik,
Thanks, it's much better now. Still, I do note some intermittent
failures.
Failed ptests:
{'libsoup': ['libsoup-3.0/multithread-test.test']}
https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/4725
Failed ptests:
{'libsoup': ['libsoup-3.0/http2-test.test']}
https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/26031
I believe we can keep it in testing for a bit of time and see which test
fails and how often, then decide if it gets merged or not. But we will
probably need a bit more work in there.
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-10-16 8:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 9:56 [OE-core][PATCH] libsoup: add ptest support Pratik Farkase
2026-10-12 17:15 ` Mathieu Dubois-Briand
2026-10-13 8:18 ` Pratik Farkase
2026-10-14 8:50 ` [OE-core][PATCH v2] " Pratik Farkase
2026-10-14 11:48 ` Mathieu Dubois-Briand
2026-10-14 12:09 ` Pratik Farkase
2026-10-14 12:07 ` [OE-core][PATCH v3] " Pratik Farkase
2026-10-16 8:05 ` Mathieu Dubois-Briand [this message]
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=DM63VLOX4BUM.15QP91UQU5UL6@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.