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] libsoup: add ptest support
Date: Mon, 12 Oct 2026 19:15:22 +0200 [thread overview]
Message-ID: <DM312DDZ2DWX.2IXZ0C78337R1@bootlin.com> (raw)
In-Reply-To: <20261012095602.19261-1-pratik.farkase@est.tech>
On Mon Oct 12, 2026 at 11:56 AM 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.
>
> header-parsing-test is excluded as it aborts in do_param_list_tests()
> with the current glib; the rest of the suite passes.
>
> Tested on qemux86-64 with ptest-runner: 34 tests, all pass.
>
> Signed-off-by: Pratik Farkase <pratik.farkase@est.tech>
> ---
Hi Pratik,
We have an upgrade to libsoup 3.8.0 that was merged a few days ago. I
could try to merge the conflicts, but as the recipe did evolve a bit, it
would mean the merged patch would be really different from what you
sent. And we should probably avoid that.
Can you rebase on top of master and send a new version please?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-10-13 17:54 UTC|newest]
Thread overview: 10+ 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2026-10-13 8:16 [OE-core][PATCH] " Pratik Farkase
2026-10-13 19:01 ` Mathieu Dubois-Briand
2026-10-14 9:43 ` Pratik Farkase
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=DM312DDZ2DWX.2IXZ0C78337R1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox