Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Siva Balasubramanian <sivakumar.bs@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: joaomarcos.costa@bootlin.com, mathieu.dubois-briand@bootlin.com,
	tim.orling@konsulko.com, JPEWhacker@gmail.com,
	Siva Balasubramanian <sivakumar.bs@gmail.com>
Subject: [OE-core][PATCH] libarchive: skip fuzz tests in ptest run
Date: Fri,  3 Jul 2026 12:30:42 +0530	[thread overview]
Message-ID: <20260703070042.3221380-1-sivakumar.bs@gmail.com> (raw)

The libarchive fuzz tests (test_fuzz_ar, test_fuzz_cab, test_fuzz_cpio,
test_fuzz_iso9660, ...) run 1000 randomised iterations per archive format
and are intended for dedicated fuzzing infrastructure rather than routine
ptest execution. On the time and memory constrained autobuilder QEMU
targets they regularly time out, e.g.:

  158: test_fuzz_iso9660    Timeout! System state:

Upstream provides the SKIP_TEST_FUZZ environment variable to skip these
tests. Export it from run-ptest so the fuzz tests are skipped rather than
run, while the rest of the test suite continues to execute normally.

[YOCTO #16340]

Signed-off-by: Siva Balasubramanian <sivakumar.bs@gmail.com>
---
 meta/recipes-extended/libarchive/libarchive/run-ptest | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/meta/recipes-extended/libarchive/libarchive/run-ptest b/meta/recipes-extended/libarchive/libarchive/run-ptest
index 6a6eb0748b..d6b4c3f934 100755
--- a/meta/recipes-extended/libarchive/libarchive/run-ptest
+++ b/meta/recipes-extended/libarchive/libarchive/run-ptest
@@ -1,5 +1,11 @@
 #!/bin/sh
 
+# The fuzz tests run 1000 randomised iterations per archive format and are
+# meant for dedicated fuzzing infrastructure, not routine ptest runs. They
+# regularly time out in the time/memory constrained autobuilder QEMU targets
+# (e.g. test_fuzz_iso9660). Skip them via the upstream escape hatch.
+export SKIP_TEST_FUZZ=1
+
 for t in libarchive_test bsdtar_test bsdcpio_test bsdcat_test bsdunzip_test; do
     ./$t
     if [ $? -eq 0 ]; then
-- 
2.34.1



                 reply	other threads:[~2026-07-03  7:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260703070042.3221380-1-sivakumar.bs@gmail.com \
    --to=sivakumar.bs@gmail.com \
    --cc=JPEWhacker@gmail.com \
    --cc=joaomarcos.costa@bootlin.com \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=tim.orling@konsulko.com \
    /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