Closed
Description
I am seeing this on the netbsd-arm-bsiegert
builder, which is a machine on my desk.
What did you expect to see?
When a given build is finished, I expect the temporary directory to be empty
What did you see instead?
After a few builds, I see:
- empty directories named
apidiff_test114645224
(numbers vary, of course) - a number of directories named
go-build335909615
and similar. Most are empty, some contain a single file named-.o
. - directories named
go-link-TestDWARF121756209
and similar, containing two files:testprog.exe
andtestprogcgo.exe
. - empty directories named
go-tool-dist-012775550
and similar. - directories named
vet_test051740249
, containing a filetestvet.exe
. - directories named
proxy-<number>
and containing a tree of downloaded modules, with.info
,.mod
and.zip
files.
While this is not a big deal per se, this means that the temp directory tends to get full, or run out of inodes over a few weeks.
We could either fix the place in the code that leaves these files behind, or maybe make the builder clean up all the remaining temp files after a build, perhaps by creating a subdirectory with the name of the build and then recursively deleting that.
Right now, I added a cronjob to clean out /var/gobuilder/tmp
but I would rather not have to.