https://autobuilder.yoctoproject.org/valkyrie/#/builders/110/builds/1113/steps/16/logs/stdio Failed ptests: {'tar': ['listing_sparse_files_bigger_than_2^33_B']} qemux86-64-musl-ptest opensuse156-vk-1 """ FAIL: listing sparse files bigger than 2^33 B sh: write error: No space left on device mkdir: can't create directory '/usr/lib/tar/ptest/tests/testsuite.dir/176': No space left on device mkdir: can't create directory '/usr/lib/tar/ptest/tests/testsuite.dir/176': No space left on device sh: write error: No space left on device ./testsuite: cd: line 2152: can't cd to /usr/lib/tar/ptest/tests/testsuite.dir/176: No such file or directory testsuite: WARNING: unable to parse test group: 176 testsuite: WARNING: A failure happened in a test group before any test could be testsuite: WARNING: run. This means that test suite is improperly designed. Please testsuite: WARNING: report this failure to <bug-tar@gnu.org>. ./testsuite: line 1936: can't create /usr/lib/tar/ptest/tests/testsuite.dir/176/testsuite.log: nonexistent directory sh: write error: No space left on device """ Full logs at: https://valkyrie.yocto.io/pub/non-release/20260904-81/testresults/qemux86-64-musl-ptest/tar.log It seems the runner when out of disk, still I'm opening just in case.
It would be good to check how much free space is left when the tar tests are running.
https://autobuilder.yoctoproject.org/valkyrie/#/builders/110/builds/1174/steps/15/logs/stdio qemux86-64-musl-ptest debian13-vk-2
I was able to reproduce this on qemux86-64 with musl. The root cause is not the host running out of disk: the sparse05 test ("listing sparse files bigger than 2^33 B") generates a file with 1000 fragments of 10 MiB of real data (~10 GiB), which cannot fit in the 1.4 GB ptest rootfs. genfile fails with ENOSPC and the test is normally reported as skipped, but the filesystem stays full for a moment, and when the autotest bookkeeping (status files, mkdir for test 176) hits that window the test is reported as FAIL and the next group cannot start. That timing explains why it looks intermittent. Patch sent to the list, skipping sparse05 and printing df at the start of run-ptest as suggested in comment 1: https://lists.openembedded.org/g/openembedded-core/topic/121269981 With the patch: 200 passed, 46 skipped, 0 failed, no ENOSPC errors.
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/4569/steps/15/logs/stdio qemux86-64-ptest debian13-vk-1 (Enzo's patch was not included in this one)
Skipped test: https://git.openembedded.org/openembedded-core/commit/?id=d48e03cf74f15f532cc65e05090d6bb36284d1bc