| Summary: | AB-INT PTEST: libarchive ptest failure: timeout in test_fuzz_iso9660 | ||
|---|---|---|---|
| Product: | [QA/Testing] Package Testing (ptest) | Reporter: | João Marcos Costa <joaomarcos.costa> |
| Component: | ptest | Assignee: | Siva Balasubramanian <sivakumar.bs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | JPEWhacker, mathieu.dubois-briand, sivakumar.bs, tim.orling |
| Version: | unspecified | ||
| Target Milestone: | 6.1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | AB-INT | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
João Marcos Costa
2026-07-01 08:23:54 UTC
Should investigate whether we should be running fuzzing tests? Perhaps the tests should be skipped. 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 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. |