Files left in /tmp after a snapcraft build

snapcraft
1

I completed a snapcraft “remote build” for 6 different architectures and I noticed that some files in /tmp were left around afterwards:

stress-ng_V0.11.22_amd64.snap.xdelta3.err
stress-ng_V0.11.22_amd64.snap.xdelta3.out
stress-ng_V0.11.22_arm64.snap.xdelta3.err
stress-ng_V0.11.22_arm64.snap.xdelta3.out
stress-ng_V0.11.22_armhf.snap.xdelta3.err
stress-ng_V0.11.22_armhf.snap.xdelta3.out
stress-ng_V0.11.22_i386.snap.xdelta3.err
stress-ng_V0.11.22_i386.snap.xdelta3.out
stress-ng_V0.11.22_ppc64el.snap.xdelta3.err
stress-ng_V0.11.22_ppc64el.snap.xdelta3.out
stress-ng_V0.11.22_s390x.snap.xdelta3.err
stress-ng_V0.11.22_s390x.snap.xdelta3.out

Although the sizes are zero, I don’t really like the idea of these junk temp files being left lying around. Can they be automatically removed once a build is complete?

2 Likes
2

Interesting, I’m not sure why those artifacts were collected to begin with. I did a quick test and was unable to reproduce, but I’ll look into it. Any thoughts where these may be coming from @cjwatson?

3

This looks more like delta uploads than remote-build

2 Likes
4

Nothing to do with Launchpad. @sergiusens’s guess of delta uploads seems a likely one to me.

2 Likes