public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: <pratik.farkase@est.tech>, <openembedded-core@lists.openembedded.org>
Cc: <pratik.farkase@ericsson.com>
Subject: Re: [OE-core][whinlatter][PATCH v1] libarchive: backport libarchive ptest to whinlatter
Date: Fri, 06 Mar 2026 19:46:06 +0100	[thread overview]
Message-ID: <DGVX7ZSLVK51.7DOWVSF56DX7@smile.fr> (raw)
In-Reply-To: <20260224150348.57934-1-pratik.farkase@est.tech>

On Tue Feb 24, 2026 at 4:03 PM CET, Pratik Farkase via lists.openembedded.org wrote:
> Backport ptest implementation from master branch to enable comprehensive
> testing of libarchive functionality in the whinlatter release.
>
> The implementation builds and installs five test suites:
> libarchive_test, bsdtar_test, bsdcpio_test, bsdcat_test, and
> bsdunzip_test, along with their test data files.
>
> Test executables for bsdtar, bsdcpio, bsdcat, and bsdunzip are
> provided via symlinks to the installed binaries.
>
> All tests on qemux86-64 pass:
>   libarchive_test: 689 tests
>   bsdtar_test: 76 tests
>   bsdcpio_test: 49 tests
>   bsdcat_test: 18 tests
>   bsdunzip_test: 8 tests
>
> This backport ensures the whinlatter branch has the same comprehensive
> test coverage as master, improving quality assurance and catching
> regressions early.
>
> Signed-off-by: Pratik Farkase <pratik.farkase@est.tech>

Hello,

I'm sorry but we decided that standalone tests like this one are not
acceptable for stable inclusion.

For more detail, see "Clarification on ptest/selftest backports for stable branches"
https://lore.kernel.org/openembedded-core/DGVX4XQ6VLWT.1HOMXA78ZXLBG@smile.fr/T/#u

Regards,
-- 
Yoann Congal
Smile ECS



      reply	other threads:[~2026-03-06 18:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24 15:03 [OE-core][whinlatter][PATCH v1] libarchive: backport libarchive ptest to whinlatter Pratik Farkase
2026-03-06 18:46 ` Yoann Congal [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=DGVX7ZSLVK51.7DOWVSF56DX7@smile.fr \
    --to=yoann.congal@smile.fr \
    --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