On Thu, 9 Mar 2023 at 12:24, Paul Gevers <elb...@debian.org> wrote: > I manually started an test run on s390x and so far (still running) the > tests consumes 100 GB of disk. I found it has a big file at least here: > > /scratch/tmp/autopkgtest-lxc.o724mxl4/downtmp/build.pyq/src/b > ffd9f21ec8/host_test.p > > # ls -alh res1-cpp.h
This file is created by a custom executable: https://github.com/mesonbuild/meson/blob/master/test%20cases/common/105%20generatorcustom/gen.c What _probably_ happens is that this piece gets stuck in an eternal loop: char c; while((c = fgetc(input)) != EOF) { fputc(c, output); } Looking at the docs, that should probably be an "unsigned char c". But the question is why did this use to work. What has changed? Something in the toolchain? If you have shell access to the problematic machines, then you can run this test manually with these commands: cd <Meson source root dir> ./meson.py test\ cases/common/105\ generatorcustom build ninja -C build
