Michael Kelly, le jeu. 01 janv. 2026 13:38:10 +0000, a ecrit: > On 29/12/2025 22:47, Samuel Thibault wrote: > > > 3) How to setup the sbuild environment to compile qtcreator package using > > > that method. > > It's just a chroot, and packages are installed/removed on each package > > build. > > I'm having no success at recreating this corruption. I'm using pbuilder to > build the qtcreator package on a 64 bit Hurd virtual machine with 3GB of > RAM.
Are you uninstalling/installing the dependencies each time? > I have run with and without mach-defpager but there is evidence to > suggest that on my machine swapping is required by the build process with > the message 'vm_page warning: unable to recycle any page' being output. That message does not mean that swapping is required, on the contrary it means that paging out didn't manage to free memory. > I have a few questions: > > 1) Does this problem occur on machines other than boralus ? Yes, the various buildds have occasionally the same kind of issue. > 2) Have the errors occurred on 32 bit Hurd as well ? All the same, yes. > I have seen stress_ng tests report bit errors which potentially could > be from the same cause. I've only seen those errors on 64 bit Hurd. That would still be worth investigating. > 3) I cannot remember if it is possible to run 64 bit without rumpdisk No, we don't plan to spend the time to make the in-gnumach drivers 64bit-ready. > 4) Are there any packages other than qtcreator that show this issue > regularly? Yes, various packages do it. For instance: sysprof: https://buildd.debian.org/status/fetch.php?pkg=sysprof&arch=hurd-i386&ver=49.0-4&stamp=1766538245&raw=0 but I guess it's actually spirv-llvm-translator-20 that got built just before that triggered the issue, without symptoms in its own build: https://buildd.debian.org/status/fetch.php?pkg=spirv-llvm-translator-20&arch=hurd-i386&ver=20.1.9-1&stamp=1766534212&raw=0 survivor: https://buildd.debian.org/status/fetch.php?pkg=survivor&arch=hurd-amd64&ver=1.0.7-6&stamp=1766520613&raw= but again, I guess it's actually rustc that triggered the issue: https://buildd.debian.org/status/fetch.php?pkg=rustc&arch=hurd-amd64&ver=1.91.1%2Bdfsg1-1~exp3&stamp=1766519978&raw=0 > 5) Finally, what is the likelihood of a build failure for qtcreator (ie. 1 > in N builds approximately) ? It's hard to say. The 4 buildds keep building packages all day long, and I notice such "stray" errors on one of them like every one day or two. > 6) Is eatmydata being used for the build? Ah, yes. (whenever the machine crashes or reboots unexpectedly, I recreate the chroots entirely) Samuel
