=== ev_ is now known as ev [11:21] wgrant: I'd like to create a launchpad-livefs-builders (or similar) team so that we can feature-flag livefs configuration/building to only be allowed for that team; that seems like the simplest way to avoid world+dog eating a ton of build time. I guess you'd need to create that in order to have it under launchpad-leader? [11:37] cjwatson: Or ~launchpad could own it. It doesn't seem like it needs to be ultra-restricted. [11:41] Mm, that would work. Indeed, I was basically planning to put ~launchpad-buildd-admins and ~ubuntu-archive in it, or something to that effect [11:41] That would sound sensible. [11:41] (also, one can transfer a team to anyone, so you could create it either way) [11:42] Oh true, duh [11:43] I tend to believe that ~launchpad-leader should own the sensitive privileged teams, but ~launchpad-livefs-builders is just to prevent abuse of resources. [11:43] AIUI [11:44] Yep [11:45] Created [12:04] cjwatson: Everything else going OK? [12:07] I think so, yeah - I need to write a garbo job, and I need to go back and refactor those livefs tests, but the rest looks like it might be dangerously close to done [12:07] er [12:07] those webservice tests, I mean [12:07] :) [12:08] oh and I still need to write the webservice-flavoured file download methods; that's the only other todo item I have left [14:20] wgrant: Is the latest buildbot failure a known transient problem? [14:20] http://lpbuildbot.canonical.com/builders/lucid_lp_lxc/builds/1149/steps/shell_9/logs/summary [14:21] I'll retry on general principles ... [14:21] cjwatson: Yeah, that's our most frequent spurious failure atm. [14:22] OK === matsubara is now known as matsubara-afk === matsubara-afk is now known as matsubara === jelmer_ is now known as jelmer