[08:36] <SpecialK|Canon> I'll take a look
[08:37] <cjwatson> It looked like William fixed that overnight but didn't mention it here
[08:37] <cjwatson> rabbitmq OOM
[08:39] <SpecialK|Canon> I saw that, but that looked to be several hours ago, and it looks like there's a bunch of builders that might be stuck cleaning
[08:43] <cjwatson> Ah, sure, feel free to dig then :)
[09:08] <SpecialK|Canon> tsimonq2: Builders reset, should now be much happier!
[18:08] <Eickmeyer> I don't know what's going on, but it seems that every day around this time some dummy recipe in a PPA takes up nearly every amd64 builder for a good half-hour. Seems suspicious to me, I don't recognize the name.
[18:10] <Eickmeyer> It also occurs whether or not the person has updated their code. Seems nobody has touched it since 2017?
[18:12] <RikMills> Eickmeyer: I guess you mean the kstars/indi ones?
[18:13] <Eickmeyer> RikMills: Yes, more like mutlaqja/libinid, but yes.
[18:13] <RikMills> it is the kstars developer
[18:14] <Eickmeyer> Ah, why is it hogging every single builder then?
[18:24] <RikMills> I have never looked that closely, but I guess he has a bazillion recipes, and in the recipes the base code is a common 'dummy' repo with each recipe nesting other repos on that
[18:25] <RikMills> so that he can build each indi driver separately I guess, instead of the whole indi source repo in one big build
[18:29] <RikMills> 100 has drivers for over 100 different types of astronomy device IIRC
[18:29] <RikMills> *indi has
[18:50] <Eickmeyer> Eesh.
[20:28] <cjwatson> Eickmeyer: It's not that user's fault.
[20:28] <cjwatson> I mean apart from having a bazillion recipes.
[20:28] <cjwatson> But it's not their fault that we aren't doing a good job of spacing them out.
[20:29] <cjwatson> However until like six hours ago it would have been very hard for us to space them out without risking tipping buildd-manager further over a performance cliff.
[20:29] <cjwatson> The situation should be better now, but I'd rather not perturb it in newly-invented ways for a while ...
[20:30] <cjwatson> The recipe build description is misleading - it doesn't show enough information to indicate that all the builds are actually distinct.
[20:30] <sarnold> it certainly sounds more like something to fiddle with near the start of a day than at the end of a day :) heh
[20:31] <cjwatson> At the moment it's not very much of a practical problem - it's noticeable if you happen to look at /builders at the right time, but it doesn't typically clog things up for too long.
[20:31] <cjwatson> (It was a good bit worse before we redeployed git.l.n on faster hardware.)
[20:33] <sarnold> yay :)
[20:38] <cjwatson> As of the rollout earlier today, buildd-manager now does a batched candidate selection query roughly once per group of builders with the same properties per scan cycle (15 seconds), rather than one query per idle builder per 15 seconds, so it's potentially much more viable to complicate the candidate selection query than it was.  But as I say I want to make sure that this actually solves the ...
[20:38] <cjwatson> ... performance problems before changing anything else there.
[20:40] <cjwatson> We think this is almost certainly related to why we've had to run two buildd-managers for the last couple of months to avoid catastrophically slow fetching of large build output files, and at least plausibly implicated in the occasional buildd-manager hangs.
[20:41] <cjwatson> Turns out that doing lots of synchronous DB queries in your asynchronous event loop is a bad idea.  (We're still doing some synchronous work there, just much less of it.)
[22:08] <Eickmeyer> cjwatson: Thanks for the info! Such a complicated topic for sure. I don't envy you your job here.
[22:23] <kyrofa> Did my build just get... paused? https://pasteboard.co/JbAxSpW.png
[22:24] <cjwatson> Link?  Impossible to grep logs for just that fragment
[22:25] <kyrofa> cjwatson, https://code.launchpad.net/~kyrofa/+snap/nextcloud-test/+build/986978
[22:25] <kyrofa> Looks like it's kinda back... but no log
[22:25] <cjwatson> It got requeued after probably some kind of network interruption to the builder I think
[22:26] <kyrofa> Ah, so it's starting over?
[22:26] <cjwatson> Yeah
[22:26] <cjwatson> Slightly odd, not sure what went on with the cancellation there
[22:26] <kyrofa> Not a big deal, just nothing I'd seen happen in the past
[22:27] <cjwatson> (Could also be that your build managed to DoS the builder in some way)
[22:27] <kyrofa> That would be interesting. Nextcloud has been building LP for years, but this is my attempt to get it using base: core18
[22:28] <kyrofa> Which also means I specified the stable channel for snapcraft as opposed to the default
[22:28] <kyrofa> Let's see if it happens again
[22:28] <kyrofa> I also changed the distribution series to bionic from xenial. Not sure if that was required or not
[22:29] <cjwatson> You should in general just leave it unset
[22:29] <cjwatson> i.e. the very misnamed "Ubuntu Core 16"
[22:29] <cjwatson> (sorry - we'll fix that soonish I hope)
[22:29] <kyrofa> Oh really? So I should distro series set to ubuntu core 16 and it'll work regardless of base?
[22:30] <kyrofa> (what about a lack of a base?)
[22:30] <cjwatson> "Ubuntu Core 16" is a really unclear way to say "build for series: 16 (i.e. what everything is) and autodetect everything else from base:"
[22:31] <cjwatson> If there's no base: it uses xenial
[22:31] <kyrofa> cjwatson, perfect, good to know, thank you! And yeah, that series 16 has thrown me in multiple places
[22:31] <kyrofa> curling the store, for example
[22:33] <kyrofa> cjwatson, interesting, that removes the arch checkbox as well, so it will depend on my having architectures set in the snapcraft.yaml?
[22:33] <cjwatson> Looks happier so far anyway
[22:33] <cjwatson> Yep
[22:34] <cjwatson> Which you should anyway, that's the modern way to spell it
[22:34] <kyrofa> Darn. I wish LP assumed I wanted the old behavior when there wasn't any architecture
[22:34] <cjwatson> snapcraft defines things according to base really