All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Burton <Ross.Burton@arm.com>
To: "pratik.farkase@est.tech" <pratik.farkase@est.tech>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	"pratik.farkase@ericsson.com" <pratik.farkase@ericsson.com>
Subject: Re: [OE-core] [PATCH v2] zstd: add ptest support
Date: Mon, 8 Jun 2026 14:05:23 +0000	[thread overview]
Message-ID: <F519FFC7-722D-42F7-B099-E6FC356B1675@arm.com> (raw)
In-Reply-To: <20260519090816.17783-1-pratik.farkase@est.tech>

On 19 May 2026, at 10:08, Pratik Farkase via lists.openembedded.org <pratik.farkase=est.tech@lists.openembedded.org> wrote:
> 
> Add comprehensive ptest support for zstd running the full upstream test
> suite covering compression correctness, streaming, dictionaries, CLI
> behavior, and fuzz testing.
> 
> Tests included:
>  - fullbench: validates all internal compression/decompression functions
>  - poolTests: thread pool ordering and synchronization
>  - invalidDictionaries: dictionary error handling
>  - legacy: legacy format (v0.4+) compatibility
>  - fuzzer: randomized compression/decompression (200s, ~700+ rounds)
>  - zstreamtest: streaming API fuzzer (90s, ~250+ rounds)
>  - decodecorpus: random frame generation and decode (30s, ~450+ rounds)
>  - playTests.sh: comprehensive CLI validation including compression,
>    decompression, multithreading, dictionaries, sparse files, frame
>    concatenation, long distance matching, benchmarks, and round-trips
>  - cli-tests: 36 Python-based CLI integration tests covering
>    compression, decompression, progress, file-stat, dictionaries,
>    symlinks, and file handling

The primary goal of the ptests is integration testing so if we’re having to manually install and run the tests then it’s entirely reasonable if not desirable to pick a subset of the tests.

In this case, we don’t need to run the fuzzer tests and so on.  I’d suggest maybe just fullbench and cli-tests would be sufficient here, less to install and faster execution.

Ross

  reply	other threads:[~2026-06-08 14:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08  8:34 [OE-core][PATCH v1] zstd: add ptest support Pratik Farkase
2026-05-19  8:34 ` Antonin Godard
2026-05-19  9:09   ` Pratik Farkase
2026-05-19  9:08 ` [PATCH v2] " Pratik Farkase
2026-06-08 14:05   ` Ross Burton [this message]
2026-08-26  8:29     ` [OE-core] " Pratik Farkase
2026-08-26  8:27   ` [OE-core][PATCH v3] " Pratik Farkase
2026-08-27 10:09     ` Alexander Kanavin
2026-08-27 11:22       ` Pratik Farkase
2026-08-27 11:52         ` Alexander Kanavin
2026-08-31  6:24   ` [OE-core][PATCH v4] " Pratik Farkase
2026-08-31  7:58     ` Mathieu Dubois-Briand
2026-08-31  8:21     ` [OE-core][PATCH v5] " Pratik Farkase
2026-09-02  7:16     ` [OE-core][PATCH v6] " 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=F519FFC7-722D-42F7-B099-E6FC356B1675@arm.com \
    --to=ross.burton@arm.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.