=== pieq_ is now known as pieq === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [12:06] 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] 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] not sure how much disk space is available for the builders [12:13] as far as I'm concerned, problem solved [12:13] 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] They have ~60GB to work with [12:18] Some ENOSPC cases are handled nicely, but not all :( [12:31] wgrant, want me to file a bug with details? [12:31] Not really :) [12:38] I had a patch to improve that lying around a while back [12:39] Fiddly to test properly though [12:41] But in any case, it's already https://bugs.launchpad.net/launchpad-buildd/+bug/1387993 [12:41] Ubuntu bug 1387993 in launchpad-buildd "builders won't automatically kill a build when "out of space"" [High,Triaged] [16:45] Does vcs import work on staging? Asking because I wanted to test out there before doing for real in live launchpad. [18:11] popey: qastaging yes, staging no [18:12] (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] cjwatson: thanks.