On 04/01/18 22:31, Josh Bowman-Matthews wrote:
I just encountered a try build failure which contained:
ar: libjs_static.a: No space left on device
I logged into the build machine and checked, and there were 5mb left out
of the 61gb disk. After checking that the machine was idle, I cleared
out 34gb worth of old builds from the target/ directories of the various
builder directories.
What can we do to avoid repeating this exercise in the future?
One of the buildbot steps is steps.Git(…, method="fresh") which removes
the target/ dir (and anything else not tracked by git)
https://github.com/servo/saltfs/blob/master/buildbot/master/files/config/factories.py#L59
But this is a done at the *start* of a job. And it looks like the same
machine can be used (not a the same time) for different kinds of jobs,
each in a separate directories. That’s how we end up with multiple
target/ dirs taking lots of space.
We probably want to keep running this step at the start of jobs to get
closer to a known state. But maybe we can *also* run it at the end, to
free up space?
I’m guessing this happened now and not before because we made a few try
builds with cargo/rustc versions that enable incremental compilation by
default, which takes a lot of space. Since we’re removing target/ for
each build, we probably should disable it explicitly. The easiest place
to do so is probably
https://github.com/servo/saltfs/blob/master/buildbot/master/files/config/environments.py#L51
. By the way, it would be nice to have this file in servo/servo so we
don’t need to do the highstate dance every time we change it.
--
Simon Sapin
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
