On 27/12/2025 20:45, Michael Kelly wrote:
On 27/12/2025 13:31, Samuel Thibault wrote:
While you are at it, we are seeing on buildds some file content
corruptions, leading to various compilation issues such as
/usr/include/i386-gnu/c++/15/bits/c++io.h:1:3: error: stray ‘\2’ in
program
This seems to be happening with builds of large programs that put
pressure on page-out and such. Notably, building qtcreator seems
stressful. The bogus content remains as such on the disk, and the bogus
content is aligned on a page boundary, so it looks as if the page was
removed and reused+overwritten before the content has hit the disk, and
thus the overwritten content is written to the disk, and reloaded as
such.
I'll try and reproduce this locally which if successful will be a
great help in identifying what's going wrong.
I've found an example of this from a build log obtained via getbuildlog:
qtcreator_17.0.1-1_hurd-amd64.log.1:/usr/include/alloca.h:1:3: error:
stray ‘\2’ in program
qtcreator_17.0.1-1_hurd-amd64.log.1:/usr/include/alloca.h:1:4: error:
stray ‘\352’ in program
In this case, the compilation fails quite early in the package build. I
haven't attempted to compile this within an sbuild environment yet. I
have however observed that stage of the package build on a 4G virtual
machine (hurd-amd64) using './debian/rules build'. Memory usage at that
stage of the build doesn't seem particularly high.
It would be helpful to know how I could simulate the buildd environment.
In particular:
1) The amount of memory available on the buildd machines typically (or
on boralus.sceen.net)
2) Whether they are used concurrently for other sbuilds whilst the
qtcreator sbuild is in operation.
3) How to setup the sbuild environment to compile qtcreator package
using that method.
Regards,
Mike.
