16340 2026-07-01 08:23:54 +0000 AB-INT PTEST: libarchive ptest failure: timeout in test_fuzz_iso9660 2026-07-23 06:58:54 +0000 1 1 10 QA/Testing Package Testing (ptest) ptest unspecified x86 Multiple RESOLVED FIXED AB-INT Medium normal 6.1 1 joaomarcos.costa sivakumar.bs JPEWhacker mathieu.dubois-briand sivakumar.bs tim.orling --- --- Don't know oldest_to_newest 106057 0 joaomarcos.costa 2026-07-01 08:23:54 +0000 https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/3890/steps/13/logs/stdio 155: test_fuzz_ar ok 156: test_fuzz_cab ok 157: test_fuzz_cpio ok 158: test_fuzz_iso9660 Timeout! System state: Collected system state: + dmesg [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x413fd0c1] [ 0.000000] Linux version 6.18.35-yocto-standard (oe-user@oe-host) (aarch64-poky-linux-gcc (GCC) 16.1.0, GNU ld (GNU Binutils) 2.46.1) #1 SMP PREEMPT Wed Jun 10 16:00:30 UTC 2026 [ 0.000000] random: crng init done [ 0.000000] Machine model: linux,dummy-virt [ 0.000000] Memory limited to 1024MB (...) qemuarm64-ptest ubuntu2404-vk-arm1 Full logs at: https://valkyrie.yocto.io/pub/non-release/20260624-47/testresults/qemuarm64-ptest/libarchive.log 106076 1 tim.orling 2026-07-02 14:53:01 +0000 Should investigate whether we should be running fuzzing tests? Perhaps the tests should be skipped. 106077 2 JPEWhacker 2026-07-02 14:54:07 +0000 It looks like libarchive has an environment variable that causes the test suite to skip fuzzing tests: SKIP_TEST_FUZZ https://github.com/libarchive/libarchive/blob/0c856d3a8f23934e77deb22f4bfc1ac0650a0b04/libarchive/test/test_fuzz.c#L62 106084 3 sivakumar.bs 2026-07-03 07:07:23 +0000 Sent a patch implementing Joshua's suggestion (comment 2): https://patchwork.yoctoproject.org/project/oe-core/patch/20260703070042.3221380-1-sivakumar.bs@gmail.com/ Sets SKIP_TEST_FUZZ=1 in run-ptest before invoking the test binaries. The fuzz tests run 1000 randomised iterations per archive format and are designed for dedicated fuzzing infrastructure, not routine ptest runs - skipping them via this upstream-provided env var keeps the remaining libarchive ptests (libarchive_test, bsdtar_test, bsdcpio_test, bsdcat_test, bsdunzip_test) running as before. Tested locally against libarchive 3.8.7: with SKIP_TEST_FUZZ=1 set, test_fuzz_iso9660 reports "skipped" immediately instead of running the fuzzing workload (verified by running the compiled test binary both with and without the variable); the remaining tests continue to pass. 106281 4 sivakumar.bs 2026-07-23 06:58:54 +0000 Patch added in master https://git.openembedded.org/openembedded-core/commit/?id=8db26e7efee024f370e8d2b45c8db24beecf61a8