[12:06] <sergiusens> not sure if it was discussed somewhere else, so FTR, oSoMoN came back and said that the build was failing as it ran out of disk space.
[12:12] <oSoMoN> yeah, every part in that snap would download and unpack a chromium source tarball (~600MB), with several copies of it (src and build directories). I removed a couple of outdated parts and that did the trick
[12:12] <oSoMoN> not sure how much disk space is available for the builders
[12:13] <oSoMoN> as far as I'm concerned, problem solved
[12:13] <oSoMoN> although it would be nice if instead of hanging indefinitely the builders would fail and report clearly that the cause of the failure is a full disk
[12:18] <wgrant> They have ~60GB to work with
[12:18] <wgrant> Some ENOSPC cases are handled nicely, but not all :(
[12:31] <oSoMoN> wgrant, want me to file a bug with details?
[12:31] <wgrant> Not really :)
[12:38] <cjwatson> I had a patch to improve that lying around a while back
[12:39] <cjwatson> Fiddly to test properly though
[12:41] <cjwatson> But in any case, it's already https://bugs.launchpad.net/launchpad-buildd/+bug/1387993
[16:45] <popey> Does vcs import work on staging? Asking because I wanted to test out there before doing for real in live launchpad.
[18:11] <cjwatson> popey: qastaging yes, staging no
[18:12] <cjwatson> (or should do anyway; we only tend to check that when we're actually working on the code import code, so it isn't very robust)
[18:12] <popey> cjwatson: thanks.