Source: golang-github-azure-azure-sdk-for-go
Version: 68.0.0-2
Severity: wishlist
Tags: upstream

Hi,

I am looking into resource usage on ci.d.n and the autopkgtest of golang-github-azure-azure-sdk-for-go shows up as needing a lot of disk space (on tmpfs, so also memory). I'm suspecting and/or hoping that a lot of it is generated for a test and then left on disk, while it's not needed for the next test. If that is true, could the test framework be enhanced to delete the files once they are no longer needed?

At the end of the autopkgtest:
root@elbrus:~# du -h --max-depth=1 /tmp/autopkgtest-lxc.ja48f1eh/downtmp/autopkgtest_tmp/obj-arm-linux-gnueabi/ 12G /tmp/autopkgtest-lxc.ja48f1eh/downtmp/autopkgtest_tmp/obj-arm-linux-gnueabi/pkg 24G /tmp/autopkgtest-lxc.ja48f1eh/downtmp/autopkgtest_tmp/obj-arm-linux-gnueabi/go-build 601M /tmp/autopkgtest-lxc.ja48f1eh/downtmp/autopkgtest_tmp/obj-arm-linux-gnueabi/src 37G /tmp/autopkgtest-lxc.ja48f1eh/downtmp/autopkgtest_tmp/obj-arm-linux-gnueabi/

Paul

PS: it seems that the test starts with running a build. Are you sure the test runs against as-installed binaries, or does it run against the build artifacts? PS2: I noticed in the build logs [1] that a lot of space is used there too, so I suspect the buildds might also profit from improvements on this front, although I'm not sure how much shared resources they have:
Build needed 00:35:12, 32559728k disk space

[1] https://buildd.debian.org/status/fetch.php?pkg=golang-github-azure-azure-sdk-for-go&arch=all&ver=68.0.0-2&stamp=1676040473&raw=0

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to