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 v1] libsolv: add ptest support
Date: Wed, 11 Feb 2026 16:27:52 +0100 [thread overview]
Message-ID: <DGC8LOGBK2YX.WBMATLDG1ZJR@bootlin.com> (raw)
In-Reply-To: <20260211122852.6057-1-pratik.farkase@est.tech>
On Wed Feb 11, 2026 at 1:28 PM CET, Pratik Farkase wrote:
> Add ptest support to enable automated testing of libsolv
> using ptest-runner.
>
> The implementation uses upstream's test infrastructure:
> testsolv binary, runtestcases.sh script, and testcase data.
> The test suite runs 28 test categories covering solver
> functionality, package dependencies, and repository handling.
>
Sorry, maybe my previous message was not clear enough: a previous
version of this patch has been merged:
https://git.openembedded.org/openembedded-core/commit/?id=f5432d1c45f9eb47182049c6930cfc6d5b26bc8d
So you have to rebase on top of it or on top of master before sending
your patch.
I can see this patch here is adding
meta/recipes-extended/libsolv/libsolv/run-ptest, which was already added
by the merged patch, so something seems to be wrong here.
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-02-11 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 12:28 [OE-core][PATCH v1] libsolv: add ptest support Pratik Farkase
2026-02-11 15:27 ` Mathieu Dubois-Briand [this message]
2026-02-13 10:13 ` Pratik Farkase
-- strict thread matches above, loose matches on Subject: below --
2026-02-02 22:36 Pratik Farkase
2026-02-10 12:03 ` Ross Burton
2026-02-10 19:05 ` 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=DGC8LOGBK2YX.WBMATLDG1ZJR@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