[buildd-tools-devel] Bug#825359: sbuild: unrealistic figure about total space used

[Johannes Schauer]

Control: severity -1 important
Control: tag -1 + moreinfo

Hi Santiago and Helge,

thanks for reporting this bug and supplying additional information to it.

On Thu, 30 Jun 2016 22:42:47 +0200 Helge Deller <deller at gmx.de> wrote:
> I'm seeing the same problem for *all* buildd logs on the hppa architecture.

I just checked out:

https://buildd.debian.org/status/package.php?p=dose3

It seems that builds generally claim to have needed ~100 MB of disk space while
hppa and sparc64 claim to have used ~400 MB of disk space. So on these two
architectures, four times more space is supposedly needed.

hppa and sparc64 are also the only architectures that seem to use sbuild 0.69.0
instead of 0.65.2 as the others do.

> For example, the "binutils" logs (see last column):
> https://buildd.debian.org/status/logs.php?pkg=binutils&arch=hppa show that
> sbuild version 0.68.0 gives a usage of 740 MB, while starting with sbuild
> version 0.69.0 it gives a usage of ~4.30 GB disc usage.

This is another interesting datapoint. The increase here is consistently about
six times of the former value.

Santiago seems to be in a situation where the multiplier was at least as high
as 80!

> The bug seems to be somewhere in the Build.pm script:
> https://anonscm.debian.org/cgit/buildd-tools/sbuild.git/log/lib/Sbuild/Build.pm
> Maybe the scanned directory list changed between versions ?
> 
> Another possibilty:
> The hppa build servers (I'm running multiple buildds on each server) all
> build the their packages in a subdirectory in /var/lib/sbuild/build/
> Maybe now the new sbuild package scans this directory and all subdirs and not
> only the /var/lib/sbuild/build/<src-package-name>/ directory?

This theory does not explain the effect that Santiago is seeing. I do also
nothing strange in the path that is passed to du in Build.pm.

Unfortunately I am also unable to reproduce the problem. The numbers of
required disk usage seemed fine to me during any of the last package builds I
did with sbuild 0.69.0-2.

Can you give me a full example that allows me to see the behaviour you witness
complete with sbuild config and schroot config if necessary?

Once this problem is fixed, I'll make another sbuild release with it.

Thank you!

cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20160701/73efa266/attachment-0001.sig>