[06:42] <cpaelzer> Eickmeyer: it isn't stuck but it is a bit short on systems atm
[06:42] <cpaelzer> plenty of systems are disabled
[06:43] <cpaelzer> probably fixing the broken autopkgtest image https://lists.ubuntu.com/archives/ubuntu-devel/2020-March/040939.html
[06:44] <cpaelzer> but in addition for the last few minutes the rest seems to be stuck in cleaning which sometimes happens
[06:44] <cpaelzer> It might resolve on its own as usual, but if anyone is around to give to give them a bump that would be even better
[06:44] <cpaelzer> cjwatson: wgrant: ^^ ?
[06:44] <wgrant> Hm, what's this about autopkgtest?
[06:45] <cpaelzer> wgrant: o/
[06:45] <wgrant> Launchpad and autopkgtest aren't particularly related, except that they run on some of the same clouds.
[06:45] <cpaelzer> wgrant: just the builders being mostly disabled and the others seem to not get out of "cleaning" state
[06:45] <cpaelzer> the magic link here is that cjwatson usually "knows what to do" and I'd expect to find him here
[06:45] <cpaelzer> I have no other reason to use this chan for that question
[06:46] <cpaelzer> well and that I thought I might reply to Eickmeyer who asked here as well
[06:46] <wgrant> This is the correct channel for Launchpad issues.
[06:46] <wgrant> But autopkgtest isn't related to Launchpad.
[06:46] <wgrant> That's an Ubuntu service; #ubuntu-devel or #ubuntu-release are more appropriate points of contact.
[06:47] <cpaelzer> hmm, my second guess would have been #IS* but you are right it is not an internal but a canonical service
[06:47] <wgrant> Canonical IS do not maintain Ubuntu's autopkgtest service.
[06:48] <wgrant> Anyway, I'm investigating the Launchpad build farm issues. But this isn't the right place to discuss services run by Ubuntu, such as autopkgtest.
[09:08] <cjwatson> cpaelzer: cjwatson uniformly redirects you to somebody else if you ask him about autopkgtest :-)
[09:08] <cjwatson> like, every time
[09:08] <cjwatson> and I do not know what to do about autopkgtest issues other than redirecting you
[09:09] <cpaelzer> Constant dripping wears away the stone :-)
[09:09] <cpaelzer> it really was about builders being stuck
[09:10] <cpaelzer> not about anything "inside" autoblktests
[09:10] <cpaelzer> wow - we might some day have aotoblktests for I/O but obviously I meant autopkgtests
[09:10] <cpaelzer> that wasn't even close on the keyboard to mistype it that way ...
[09:11] <cjwatson> Well, more precisely about the system that resets builder VMs being stuck
[09:11] <cpaelzer> agreed
[09:36] <jamespage> morning - I foobared a new project setup this morning - is it possible to change its LP name - https://launchpad.net/trilio-data-mover
[09:36] <jamespage> trilio-data-mover -> charm-trilio-data-mover
[09:36] <jamespage> ?
[09:41] <cjwatson> jamespage: done
[09:41] <jamespage> cjwatson: thankyou!
[14:33] <Laney> which team can set a distro's status (e.g. freezing the archive) and create new series? assuming it's the same role that can do both
[14:33] <Laney> is it the maintainer? i.e. ~techboard for Ubuntu
[14:44] <cjwatson> Laney: Exactly
[14:45] <cjwatson> (~ubuntu-drivers can create series too, I think.  But ~techboard can do it all)
[14:54] <Eickmeyer[m]> cpaelzer: No, I was just falling victim to pkgstripfiles being molasses-slow. Perhaps even glacial slow. I have yet to come up with the correct slow analogy.
[15:09] <cpaelzer> hehe
[15:09] <cpaelzer> Eickmeyer[m]: was it the lock loop that sometimes happens - or just standing at that lein for a loooong time?
[15:10] <Eickmeyer[m]> cpaelzer: It was the lock loop. Easily reproducable if I update ubuntustudio-look in the archive.
[15:11] <Eickmeyer[m]> Like, every time I updated it would take an hour to build, whereas it would take < 1min locally.
[15:11] <Eickmeyer[m]> My computer is cool, but it's not THAT cool.
[15:13] <cjwatson> It should reproduce locally if you install pkgbinarymangler in the chroot.
[15:13] <cjwatson> This is a package that implements various bits of Ubuntu policy for builds.
[15:13] <Eickmeyer[m]> Well, I could try that, but not sure it's worth it at this point.
[15:13] <Eickmeyer[m]> But, is that a bug?
[15:13] <cjwatson> Wouldn't be too surprising for it to have some race issues.
[15:14] <cjwatson> We could debate semantics of what counts as a bug, but it doesn't sound like terribly desirable behaviour as it stands.
[15:14] <Eickmeyer[m]> That's what I was thinking. It looked like some sort of race condition.
[15:14] <cjwatson> It's a long time since I looked at it though, and it's owned by Ubuntu rather than by Launchpad.
[15:14] <Eickmeyer[m]> Right, that makes sense.
[16:07] <seb128> cjwatson, hey, thanks for reviewing/approving my launchpad change :)
[16:07] <seb128> I got a buildbot failure email, I guess that's following that mp approval
[16:07] <seb128>  http://lpbuildbot.canonical.com/builders/lp-devel-xenial/builds/1099 ... is there anything I need to do about it?
[16:11] <cjwatson> seb128: Our test suite is sadly not 100% reliable.  Not your problem in this case - I've retried the test
[16:11] <seb128> cjwatson, thanks!
[16:12] <cjwatson> (It's close, but with over 20000 tests it doesn't take much to trip it ...)
[16:12] <cjwatson> Thanks for the MP :)
[16:33] <RikMills> cjwatson: does buildd-manager need a poke?
[16:44]  * cjwatson moves the help contact to the start of the topic so that people are more likely to notice it
[16:44] <cjwatson> that said; requested a bounce
[16:44] <RikMills> ohhh. sorry
[16:50] <cjwatson> Back up now, and I've filed https://bugs.launchpad.net/launchpad/+bug/1866868
[16:51] <RikMills> great :)
[16:52]  * RikMills subscribes
[16:53] <cjwatson> But yeah, we're trying to move a bit more towards a help contact system rather than it always being "ask Colin or William"
[16:54] <cjwatson> Which is less appropriate now that we have more people on the team