On Wed, 8 Mar 2023 at 20:47, Paul Gevers <elb...@debian.org> wrote: > Having said that, let me open the discussion on what I expect from this > bug. I *don't* expect all tests on our infrastructure to be totally > resilient to all restrictions we have. Although several tens of GB is a > lot, I also realize that it isn't *that* much, so if you understand why > meson suddenly needs considerably more disk space and that's to be > expected, then I'm fine with closing this bug and have meson on the
In my opinion this is definitely a bug. I don't know where, though. Whenever I do a new release I run a full package build + test suite run and all that in an isolated VM (with pbuilder). That image has only a single 40 GB file system. I have never had a problem with disk space usage even though this image has all the dependency packages installed twice: once on the main install and once in pbuilder. I just checked and the image has 8 GB of free disk space so doing a full package rebuild should take less than that.
